[JDEV] client proposal
Scott Robinson
scott at tranzoa.com
Wed Sep 8 16:18:28 CDT 1999
Interleaved response.
Scott.
* Ryan Eatmon translated into ASCII [Wed, Sep 08, 1999 at 03:16:56PM -0500][<37D6C438.514986E7 at ti.com>]
>
> Hi, I'm new to the list but thought I'd throw in some input.
Welcome to the Jabber project!
>
> Since this is going to be an XML based transport, wouldn't it make sense
> for the Jabber clients to format the message in XML? Then it would be
> the server's responsibility to reformat the message into the target
> transports message format. Or if the message is going to another Jabber
> client it would passed straight through.
>
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.
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.
[snap]
> Ryan Eatmon reatmon at ti.com
> -----------------------------------------
> Mixed Signal Product Development EDA Team
>
[snap]
More information about the JDev
mailing list