[JDEV] Why XML for everything?

[Bill Ataras]

Jabber also will support whatever the ultimate IETF standards are. This may
have an impact on the XML thing. If the world goes IETF and IETF isn't XML,
wouldn't XLM then be relegated to just "native" jabber client->server and
not server->server->non-jabber-client ?


-----Original Message-----
From: Patrick McCuller <patrick at kia.net>
To: jdev at jabber.org <jdev at jabber.org>
Date: Wednesday, September 29, 1999 8:43 PM
Subject: RE: [JDEV] Why XML for everything?


>[...]
>
>> So, for example, instead of a message like one of your example
>> messages:
>>
>> <message>
>
>[...]
>
>> </message>
>>
>> You might have the following:
>>
>> [packet type byte]
>> [1-2 other fixed bytes]
>> [4 bytes-from ID]
>> [4 bytes-to ID]
>> [data length byte]
>> Subject: Here's a subject of you want one.
>> Who needs threads?  I just want to send my buddy at message! :-)
>> Here you can have all kinds of XML (or HTML) attributes, fonts, etc...
>> asdgf asdfkjasgoijqwert asdgaldgjkas
>> <NULL>
>>
>
> I suggest you give it up. You will never convince the Jabber team to
change
>the Jabber protocol away from XML, and whatever valid points you may make
>won't make anyone happier. Jabber is defined as an XML-based instant
>messaging protocol, and good or bad, however strong your arguments, they
>will not affect the fundamental nature of Jabber.
>
> Try putting your thoughts on the IMPP list; there's lots of that there.
Try
>developing a competing instant messaging system. How about an alternative
>Jabber transport? I encourage you to do whatever you like to further your
>approach to this technology, but you are wasting your time with this on the
>jdev list.
>
>
>Patrick
>
>
>_______________________________________________
>jdev mailing list
>jdev at jabber.org
>http://mailman.jabber.org/listinfo/jdev