[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] about message key oid

Cyrille Giquello wrote:

Hello,

I'm thinking on the architecture of a new project and XmlBlaster will be the earth of it.
So, I need to study it in a fine way... what's hard for me !!
;oP

Is there advantages to force the message's key oid ?
Is it a performance hint ?


Yes you should prefer to name your kay oids (==topics) to avoid temporary
topic creation and deletion.

Should I use short key oid and put other data in sub key elements ?

for example:

prop1:
<key oid='bsm.admin' contentMime='text/xml'>
  <app>tools.freequestion</app>
  <command>validate</command>
</key>

prop2:
<key oid='bsm.admin.tools.freequestion.validate' contentMime='text/xml'>
</key>

For broadcast update, multiple subscribtion, fast distribution is there some preference between the two above propositions ?

Both is perfectly valid.
The markup should ease the possibility to query topics you need in your use case
with xpath. If you have only well named topic you probably never need xpath queries.

Marcel


I hope it is not a tedious question ... ...

cyrille