On (Tue) Feb 01 2011 [10:54:53], Andrew Beekhof wrote:
On Tue, Feb 1, 2011 at 10:41 AM, Amit Shah
<amit.shah(a)redhat.com> wrote:
> On (Tue) Feb 01 2011 [10:35:55], Andrew Beekhof wrote:
>> On Sat, Jan 29, 2011 at 5:19 AM, Amit Shah <amit.shah(a)redhat.com> wrote:
>> > On (Fri) Jan 28 2011 [11:28:55], Perry Myers wrote:
>> >> (for reference we're talking about making changes to libvirt
default
>> >> configurations to always include virtio-serial channels so that
Matahari
>> >> can use it w/o asking end users to add these themselves)
>> >
>> > ...
>> >
>> >> Ok. So what we'd want here is to by default add a virtio-serial
channel
>> >> in virtinst and vdsm with a name like
'org.matahari-project.port' (or if
>> >> we want to be more generic to this just being a qpid transport it
could
>> >> be org.apache.qpid.port)
>> >
>> > I'd prefer org.matahari-project.qpid.
>>
>> s/-// to make it consistent with the class scope (qpid doesn't like dashes)
>>
>> > This channel is used by the
>> > Matahari project, not the Apache qpid project, right?
>>
>> Technically speaking any qpid agent could be using it, not just matahari ones.
>
> Would all the agents using the same key-value pairs / commands / etc.?
>
I don't understand the question, the agents have no understanding of
the transports over which qpid is sending messages.
I'm talking of the message itself: can all qpid messages be interpreted
the same way by any agent that will / can be written? As in is there
nothing specific to matahari that will flow over this new channel?
Amit