You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Ming Zhang <bl...@gmail.com> on 2009/10/12 22:56:34 UTC

qmf protocol

Hi All

Read this http://qpid.apache.org/qmf-protocol.html and have a question about it.

"This message contains a content record. Content records contain the
values of all properties or statistics in an object. Such records are
broadcast on a periodic interval if 1) a change has been made in the
value of one of the elements, or 2) if a new management client has
bound a queue to the management exchange."

If a full content record is sent for any value change, this sounds
very expensive. Why not only send up the changed value?

Did I misunderstand something?


Ming

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: qmf protocol

Posted by Ming Zhang <bl...@gmail.com>.
ic. sounds much reasonable. thanks for the explanation.

the more i look at it, the more i think qmf is a right choice. now
just need to find more complete examples.

Ming


On Mon, Oct 12, 2009 at 5:10 PM, Carl Trieloff <cc...@redhat.com> wrote:
>
> if the mgnt interval is 10 seconds for the agent, then the value can change
> n times, and only 1 update will
> be sent at the 10 second mark.
>
> if you care about hi/low etc, these are data types in QMF, that can give you
> current/hi/low value
> etc for the inteval.
>
> Alternatively you can 'pull' the data you care about when you care about it
> and not subscribe to the auto
> publish.
>
> Carl.
>
>
> Ming Zhang wrote:
>>
>> ok. so if only changed value is sent out, if agent code change value
>> 1, then value 2, will 2 messages sent out? that is still expensive? or
>> need to have a explicitly push action so multi change will be combined
>> in one message, which supposed to be more efficient? thanks.
>>
>>
>>
>> Ming
>>
>>
>> On Mon, Oct 12, 2009 at 4:59 PM, Carl Trieloff <cc...@redhat.com>
>> wrote:
>>
>>>
>>> Ming Zhang wrote:
>>>
>>>>
>>>> Hi All
>>>>
>>>> Read this http://qpid.apache.org/qmf-protocol.html and have a question
>>>> about it.
>>>>
>>>> "This message contains a content record. Content records contain the
>>>> values of all properties or statistics in an object. Such records are
>>>> broadcast on a periodic interval if 1) a change has been made in the
>>>> value of one of the elements, or 2) if a new management client has
>>>> bound a queue to the management exchange."
>>>>
>>>> If a full content record is sent for any value change, this sounds
>>>> very expensive. Why not only send up the changed value?
>>>>
>>>> Did I misunderstand something?
>>>>
>>>
>>> only value that have changed after the initial broadcast or send on an
>>> aggregated basis on the mgnt interval
>>>
>>> Carl.
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>>
>
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: qmf protocol

Posted by Carl Trieloff <cc...@redhat.com>.
if the mgnt interval is 10 seconds for the agent, then the value can 
change n times, and only 1 update will
be sent at the 10 second mark.

if you care about hi/low etc, these are data types in QMF, that can give 
you current/hi/low value
etc for the inteval.

Alternatively you can 'pull' the data you care about when you care about 
it and not subscribe to the auto
publish.

Carl.


Ming Zhang wrote:
> ok. so if only changed value is sent out, if agent code change value
> 1, then value 2, will 2 messages sent out? that is still expensive? or
> need to have a explicitly push action so multi change will be combined
> in one message, which supposed to be more efficient? thanks.
>
>
>
> Ming
>
>
> On Mon, Oct 12, 2009 at 4:59 PM, Carl Trieloff <cc...@redhat.com> wrote:
>   
>> Ming Zhang wrote:
>>     
>>> Hi All
>>>
>>> Read this http://qpid.apache.org/qmf-protocol.html and have a question
>>> about it.
>>>
>>> "This message contains a content record. Content records contain the
>>> values of all properties or statistics in an object. Such records are
>>> broadcast on a periodic interval if 1) a change has been made in the
>>> value of one of the elements, or 2) if a new management client has
>>> bound a queue to the management exchange."
>>>
>>> If a full content record is sent for any value change, this sounds
>>> very expensive. Why not only send up the changed value?
>>>
>>> Did I misunderstand something?
>>>       
>> only value that have changed after the initial broadcast or send on an
>> aggregated basis on the mgnt interval
>>
>> Carl.
>>
>> ---------------------------------------------------------------------
>> 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
>
>   


Re: qmf protocol

Posted by Ming Zhang <bl...@gmail.com>.
ok. so if only changed value is sent out, if agent code change value
1, then value 2, will 2 messages sent out? that is still expensive? or
need to have a explicitly push action so multi change will be combined
in one message, which supposed to be more efficient? thanks.



Ming


On Mon, Oct 12, 2009 at 4:59 PM, Carl Trieloff <cc...@redhat.com> wrote:
> Ming Zhang wrote:
>>
>> Hi All
>>
>> Read this http://qpid.apache.org/qmf-protocol.html and have a question
>> about it.
>>
>> "This message contains a content record. Content records contain the
>> values of all properties or statistics in an object. Such records are
>> broadcast on a periodic interval if 1) a change has been made in the
>> value of one of the elements, or 2) if a new management client has
>> bound a queue to the management exchange."
>>
>> If a full content record is sent for any value change, this sounds
>> very expensive. Why not only send up the changed value?
>>
>> Did I misunderstand something?
>
> only value that have changed after the initial broadcast or send on an
> aggregated basis on the mgnt interval
>
> Carl.
>
> ---------------------------------------------------------------------
> 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


Re: qmf protocol

Posted by Carl Trieloff <cc...@redhat.com>.
Ming Zhang wrote:
> Hi All
>
> Read this http://qpid.apache.org/qmf-protocol.html and have a question about it.
>
> "This message contains a content record. Content records contain the
> values of all properties or statistics in an object. Such records are
> broadcast on a periodic interval if 1) a change has been made in the
> value of one of the elements, or 2) if a new management client has
> bound a queue to the management exchange."
>
> If a full content record is sent for any value change, this sounds
> very expensive. Why not only send up the changed value?
>
> Did I misunderstand something?

only value that have changed after the initial broadcast or send on an 
aggregated basis on the mgnt interval

Carl.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org