[JDEV] client proposal

[Ryan Eatmon]

> This is currently a thing "in transitition." Blue-skies, 
> the Jabber message will have a standard format and a 
> client or transport (if they wanted) could add random 
> fragments whereever they pleased.

Of course.  In a perfect world everything would work perfectly the first
time, but this is reality and we have to start somewhere.  The beauty of
starting with XML as the formatting is that you can expand it in the
future and reach the perfection.  And it isn't painful to do.  That is
presumably why you chose to use XML as the transport language (a good
choice and good use of the language IMHO).


> However, we've added a little coherency to our protocol. 
> There is a tag called <ext/> which should be used by 
> message modifiers to hold non-standard extensions.

I'm a little confused by what exactly you mean by that...  Are you
saying that *are* using XML for the message body formatting but not
dictating the base level of formatting supported by all clients?



-- 

Ryan Eatmon                reatmon at ti.com
-----------------------------------------
Mixed Signal Product Development EDA Team