[JDEV] cons of jabber technology

[Robert Temple]

I'm pretty sure that everyone knows the "PROS" of using
XML for the protocol, but there is a "CON" or two regarding 
the use of XML:

1st, Parsing XML requires considerably more processing then 
a binary or a simpler ASCII protocol.  Its possible that the
server could be overwhelmed with parsing XML.  Although it 
is far more likely that network congestion will be a scale 
issue before processor congestion.

2nd, Using XML requires that all clients have access to 
an XML parser.  Most of the time this means that the clients 
need to ship with XML parsing code.  Typically this will add 
at least 150k extra to a client's download size.  For some 
clients its considerably more.  In the future this might not
be an issue at all, since more and more OSs are shipping 
with DOM & SAX support built in.

-Robert

-----Original Message-----
From: siddharth thakkar [mailto:sjthakkar at yahoo.com]
Sent: Saturday, February 10, 2001 8:19 AM
To: jdev at jabber.org
Subject: [JDEV] cons of jabber technology


hi , all the great developers of Jabber.

  I have undertook a project on Jabber Technology. And
as a part of Study of Jabber Technology, I need to
prepare the article describing ANY NEGATIVE FACTORS,
RISKS, OR VULNERABILITIES EXISTING WITH JABBER
TECHNOLOGY.

  The positive and encouraging facts of Jabber, I have
found at many places; but what i need is Potential
Hazards, or Risks of the Jabber Technology.

   Do reply soon, IT WILL BE A GREAT ENCOURAGEMENT FOR
MY STUDY OF JABBER TECHNOLOGY and will make me
understand Jabber better.

   Thanking you all in advance,

yours truly,
siddharth
sjthakkar at yahoo.com
sjthakkar at usa.net

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev