Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 93983 invoked from network); 12 Oct 2009 17:31:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Oct 2009 17:31:39 -0000 Received: (qmail 67170 invoked by uid 500); 12 Oct 2009 17:31:39 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 67139 invoked by uid 500); 12 Oct 2009 17:31:38 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 67129 invoked by uid 99); 12 Oct 2009 17:31:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Oct 2009 17:31:38 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tross@redhat.com designates 209.132.183.28 as permitted sender) Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Oct 2009 17:31:36 +0000 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9CHVE34018817 for ; Mon, 12 Oct 2009 13:31:15 -0400 Received: from dhcp-100-18-254.bos.redhat.com (dhcp-100-18-254.bos.redhat.com [10.16.18.254]) by int-mx05.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n9CHVE2R024194 for ; Mon, 12 Oct 2009 13:31:14 -0400 Message-ID: <4AD367E3.7050606@redhat.com> Date: Mon, 12 Oct 2009 13:31:15 -0400 From: Ted Ross User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: users@qpid.apache.org Subject: Re: dynamic expand schema References: <93552bad0910091519o4d9002e1pb50f314760b7a860@mail.gmail.com> In-Reply-To: <93552bad0910091519o4d9002e1pb50f314760b7a860@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 10.5.11.18 If you look at the python agent test in "qpid/cpp/bindings/qmf/tests/python_agent.py", you will see that the schema is built up programatically. You can add new elements to the schema as you go along. If you always add content (don't delete or rename), you can minimize the disruption experienced by your console code. QMF will handle multiple different definitions for the same schema classes (it creates a "class-key" that consists of package name, class name, and a hash (MD5) of the schema). This ensures that a console that is working with both versions will not misinterpret the data. -Ted Ming Zhang wrote: > Hi All > > If I use QMF schema to describe a host, it is quite possible that I > will add cpu statistics today, and memory data tomorrow. this means i > have to change the schema from time to time. what is the good practice > for this? Do I have to recompile the schema, change the code, and > shutdown my current agent and start a new one? or i have a way to > dynamically add some as a plugin like architecture? Thanks. > > Ming > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:users-subscribe@qpid.apache.org > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:users-subscribe@qpid.apache.org