[jdev] Re: jdev Digest, Vol 10, Issue 4
Kamran Zafar
dearkami at yahoo.com
Fri Nov 5 03:55:35 CST 2004
> TLS is a binary protocol, and the negotiation is an
> exchange of packets
> between the client and server to trade public keys
> and decide on security
> parameters. This negotiation, as well as the rest
> of the TLS protocol, is
> covered in RFC 2246.
> http://www.faqs.org/rfcs/rfc2246.html
>
> However, most everyone just uses a library for this,
> such as OpenSSL.
Justin,
Ok I will be going through this RFC.
In the meantime, can you please give me a rough idea
of an estimation (in terms of hours or days)if i have
to provide implementation/support for TLS and SALS
(Note: I have already developed a xmpp compliant
client and server
applications with most of the features.).
And what do you mean by "most everyone just uses a
library for this". From where can I get this library
and would this be helpful for me since my development
is in c-sharp?
Your help will be highly appreciated.
Regards,
Kamran
--- jdev-request at jabber.org wrote:
> Send jdev mailing list submissions to
> jdev at jabber.org
>
> To subscribe or unsubscribe via the World Wide Web,
> visit
> http://mail.jabber.org/mailman/listinfo/jdev
> or, via email, send a message with subject or body
> 'help' to
> jdev-request at jabber.org
>
> You can reach the person managing the list at
> jdev-owner at jabber.org
>
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of jdev digest..."
>
>
> Today's Topics:
>
> 1. Re: jdev Digest, Vol 10, Issue 3 (Kamran
> Zafar)
> 2. TCP Packet Construction (Jon Phillips)
> 3. Re: TLS negotiation (kavitha e)
> 4. Re: Re: jdev Digest, Vol 10, Issue 3 (Justin
> Karneges)
> 5. RE: TCP Packet Construction (Heiner Wolf)
> 6. Re: TCP Packet Construction (Jon Phillips)
> 7. Re: TLS negotiation (aliban at gmx.net)
> 8. Re: TCP Packet Construction (aliban at gmx.net)
>
>
>
----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 4 Nov 2004 21:23:21 -0800 (PST)
> From: Kamran Zafar <dearkami at yahoo.com>
> Subject: [jdev] Re: jdev Digest, Vol 10, Issue 3
> To: jdev at jabber.org
> Message-ID:
> <20041105052321.89604.qmail at web60803.mail.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Alexey,
>
> Thanks for your reply and giving the reference of
> RFC
> 3920.
>
> Yes, I have gone through this RFC (specially
> "section
> 5. Use of TLS"). But my confusion is still there.I
> have a perfect understanding of how and what stanzas
> should be passed through client-server-client.
>
> Let me explain my question in other way,
>
> In RFC 3920, please go to (section "5.3.
> Client-to-Server Example"). There is written:
>
> Step 4: Client sends the STARTTLS command to server:
> <starttls
> xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
>
> Step 5: Server informs client that it is allowed to
> proceed:
> <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
>
> Step 6: Client and server attempt to complete TLS
> negotiation over the existing TCP connection.
>
> Step 7: If TLS negotiation is successful, client
> initiates a new stream to server:
>
> I want to know what exactly happens in the "TLS
> negotiation" (implementation point of view). What I
> have to do (other than making and send/receiving of
> TLS related stanzas) in my client and server
> application in "step 6"?
>
> I hope this time I am more explanatory.
>
> Regards,
> Kamran
>
>
>
>
>
> --- jdev-request at jabber.org wrote:
>
> > Send jdev mailing list submissions to
> > jdev at jabber.org
> >
> > To subscribe or unsubscribe via the World Wide
> Web,
> > visit
> > http://mail.jabber.org/mailman/listinfo/jdev
> > or, via email, send a message with subject or body
> > 'help' to
> > jdev-request at jabber.org
> >
> > You can reach the person managing the list at
> > jdev-owner at jabber.org
> >
> > When replying, please edit your Subject line so it
> > is more specific
> > than "Re: Contents of jdev digest..."
> >
> >
> > Today's Topics:
> >
> > 1. TLS negotiation (Kamran Zafar)
> > 2. Re: TLS negotiation (Alexey Nezhdanov)
> >
> >
> >
>
----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Thu, 4 Nov 2004 02:33:14 -0800 (PST)
> > From: Kamran Zafar <dearkami at yahoo.com>
> > Subject: [jdev] TLS negotiation
> > To: jdev at jabber.org
> > Message-ID:
> >
> <20041104103314.69660.qmail at web60806.mail.yahoo.com>
> > Content-Type: text/plain; charset=us-ascii
> >
> > Hi,
> >
> > I have developed a xmpp compliant client and
> server
> > applications with most of the features.
> >
> > Now I want to give (client 2 server )TLS
> > implementation in it.
> >
> > Please let me know what should i need to do in my
> > existing coding in order to add this feature.
> >
> > Regards,
> > Kamran
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Check out the new Yahoo! Front Page.
> > www.yahoo.com
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Thu, 4 Nov 2004 13:37:07 +0300
> > From: Alexey Nezhdanov <snake at penza-gsm.ru>
> > Subject: Re: [jdev] TLS negotiation
> > To: Jabber software development list
> > <jdev at jabber.org>
> > Message-ID:
> <200411041337.07598.snake at penza-gsm.ru>
> > Content-Type: text/plain; charset="koi8-r"
> >
> > ÷ ÓÏÏÂÝÅÎÉÉ ÏÔ þÅÔ×ÅÒÇ 04 îÏÑÂÒØ 2004 13:33 Kamran
> > Zafar ÎÁÐÉÓÁÌ(a):
> > > Hi,
> > >
> > > I have developed a xmpp compliant client and
> > server
> > > applications with most of the features.
> > What language/license/download location ?
> > >
> > > Now I want to give (client 2 server )TLS
> > > implementation in it.
> > >
> > > Please let me know what should i need to do in
> my
> > > existing coding in order to add this feature.
> > Did you read RFC 3920? I think there is very good
> > description of how TLS
> > should be done. If yes - then eveluate your
> question
> > in more words please.
> > >
> > > Regards,
> > > Kamran
> >
> >
> > --
> > Respectfully
> > Alexey Nezhdanov
> >
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mail.jabber.org/mailman/listinfo/jdev
> >
> >
> > End of jdev Digest, Vol 10, Issue 3
> > ***********************************
> >
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Check out the new Yahoo! Front Page.
> www.yahoo.com
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 05 Nov 2004 14:31:41 +0900
> From: Jon Phillips <jon at rejon.org>
> Subject: [jdev] TCP Packet Construction
> To: Jabber software development list
> <jdev at jabber.org>
> Message-ID: <418B103D.6060102 at rejon.org>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> Hello,
>
> I interested to know if there are any good
> resources, documents, or
> source code I could look at to see how to properly
> receive packets from
> a jabber server like jabberd (which I am using) via
> TCP and then how to
> receive and reconstruct the entire packet.
>
> I'm using Visual Studio .net and WINSOCK to do
> connection and receiving.
> Right now I have a working client that receive
> packets that are 8129
> bytes, but these packets might not contain the full
> message. This
> problem gets worse with more traffic.
>
> What is the best way to construct entire jabber
> server packets into
> comlete packets/message. For example, the server
> might send a user's
> message in xml, and because of web traffic the
> complete message might
> not arrive in teh received 8192 bytes...
>
> Other than this problem, my custom jabber client for
> this game,
> gopetslive.com is going pretty well.
>
> Any help or code sample or pointers would be much
> appreciated.
>
> Thanks,
> Jon
>
> --
> Jon Phillips
>
> KOREA.PH.010.3140.7483
> USA.PH.858.361.2811
> jon at rejon.org
> http://www.rejon.org
>
> Inkscape (http://inkscape.org)
> Open Clip Art Library (www.openclipart.org)
> CVS Book (http://cvsbook.ucsd.edu)
> Scale Journal (http://scale.ucsd.edu)
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 4 Nov 2004 21:36:24 -0800 (PST)
> From: kavitha e <kavi_el at yahoo.com>
> Subject: Re: [jdev] TLS negotiation
> To: Jabber software development list
> <jdev at jabber.org>
> Message-ID:
> <20041105053624.32093.qmail at web20328.mail.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
>
> Hi Kamran,
>
> I am new to this jabber, i am just going thru
> RFC's,i
> cant help you, but i need your help if you dont
> mind.
>
> You said u have developed xmpp complient C/S
> applications can you just tell me how to do that?
>
> I have to create an application to access jabber
> server & its transports for MSN & Yahoo messengers.
> More clearly, i need access the API provided by
> Jabber
> server through xml protocols.
>
> Can you suggest me how to go about it? What are the
> jabber servers i need to download? What are steps i
> need to follow?
>
> Please help me...
>
> Thanks & Regards
> Kavitha
> --- Kamran Zafar <dearkami at yahoo.com> wrote:
>
> > Hi,
> >
> > I have developed a xmpp compliant client and
> server
> > applications with most of the features.
> >
> > Now I want to give (client 2 server )TLS
> > implementation in it.
> >
> > Please let me know what should i need to do in my
> > existing coding in order to add this feature.
> >
> > Regards,
> > Kamran
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Check out the new Yahoo! Front Page.
> > www.yahoo.com
> >
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mail.jabber.org/mailman/listinfo/jdev
> >
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Check out the new Yahoo! Front Page.
> www.yahoo.com
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 4 Nov 2004 21:37:38 -0800
> From: Justin Karneges
> <justin-keyword-jabber.093179 at affinix.com>
> Subject: Re: [jdev] Re: jdev Digest, Vol 10, Issue 3
> To: Jabber software development list
> <jdev at jabber.org>
> Message-ID:
>
>
<200411042137.38709.justin-keyword-jabber.093179 at affinix.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Thursday 04 November 2004 09:23 pm, Kamran Zafar
> wrote:
> > Step 5: Server informs client that it is allowed
> to
> > proceed:
> > <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
> >
> > Step 6: Client and server attempt to complete TLS
> > negotiation over the existing TCP connection.
> >
> > Step 7: If TLS negotiation is successful, client
> > initiates a new stream to server:
> >
> > I want to know what exactly happens in the "TLS
> > negotiation" (implementation point of view). What
> I
> > have to do (other than making and send/receiving
> of
> > TLS related stanzas) in my client and server
> > application in "step 6"?
>
> TLS is a binary protocol, and the negotiation is an
> exchange of packets
> between the client and server to trade public keys
> and decide on security
> parameters. This negotiation, as well as the rest
> of the TLS protocol, is
> covered in RFC 2246.
> http://www.faqs.org/rfcs/rfc2246.html
>
> However, most everyone just uses a library for this,
> such as OpenSSL.
>
> -Justin
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 5 Nov 2004 07:19:43 +0100
> From: "Heiner Wolf" <wolf at bluehands.de>
> Subject: RE: [jdev] TCP Packet Construction
> To: "Jabber software development list"
> <jdev at jabber.org>
> Message-ID:
>
>
<11D121AB355B69448D3A9F2132D2A3AA4202A9 at niobe.BlueHands.de>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> >I interested to know if there are any good
> resources, documents, or
> >source code I could look at to see how to properly
> receive
> >packets from a jabber server like jabberd (which I
> am using) via TCP and
> >then how to receive and reconstruct the entire
> packet.
>
> When you deal with TCP as in the case of Jabber,
> then you must not think in terms of 'packets'. Both
> parties will receive a stream of bytes. While they
> send chunks of data on the connection, there is no
> guarantee that the receiver gets the data in the
> original chunks. The only guarantees that TCP gives
> are 1. that the data will arrive or you get an error
> 2. the byte order will be retained. Again: the
> receiver might get the data in totally different
> 'packets'.
>
> >I'm using Visual Studio .net and WINSOCK to do
> connection and
> >receiving. Right now I have a working client that
> receive packets that
> >are 8129 bytes, but these packets might not contain
> the full message.
> >This problem gets worse with more traffic.
>
> What you must do is: forward every piece of data to
> the protocol parser. In this case it is an XML
> parser. The XML parser must be able to parse
> 'incomplete' XML and tell you about the structure
> before the main wrapper tag is closed. People call
> it a SAX parser as opposed to DOM parsers. You need
> a SAX parser. You feed it with every byte that comes
> from the connection. There is virtually nothing
> between the read() system call where you get data
> from the connection and the parse() where you
> forward the data to the parser. The parser will
> consume the bytes. The parser will tell you when a
> first order tag is finished. That would be something
> like a <message/> or <presence/> inside a
> <stream:stream>. If this happens then you can
> analyze the first order tag. That's then called a
> stanza in Jabber terms. In XML terms it is just the
> first order sub tag of the XML wrapper tag.
>
> >What is the best way to construct entire jabber
> server packets into
> >comlete packets/message. For example, the server
> might send a user's
> >message in xml, and because of web traffic the
> complete message might
> >not arrive in teh received 8192 bytes...
>
> I reiterate, because this is important: this is TCP.
> There are no messages. Your network API will give
> you multiple bytes at once. This looks like a
> message. You don't care. You handle all data to the
> XML parser. The parser will tell you when stanzas
> are complete. You are probably testing in your lab.
> Over the wide internet you might even get smaller
> pieces of data at once (like 500 bytes). Stanzas
> might be split badly. There might be even the last
> '>' missing. Don't look at the data directly. Let
> the XML parser look. It will tell you when a stanza
> is complete.
>
> >Other than this problem, my custom jabber client
> for this game,
> >gopetslive.com is going pretty well.
> >
> >Any help or code sample or pointers would be much
> appreciated.
>
> hw
> --
> Dr. Klaus H. Wolf
> bluehands GmbH & Co.mmunication KG
> http://www.bluehands.de/people/hw
> +49 (0721) 16108 75
> --
> Jabber enabled Virtual Presence on the Web:
> http://www.lluna.de/
> Open Source Future History:
> http://www.galactic-developments.com/
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 05 Nov 2004 17:06:09 +0900
> From: Jon Phillips <jon at rejon.org>
> Subject: Re: [jdev] TCP Packet Construction
> To: Jabber software development list
> <jdev at jabber.org>
> Message-ID: <418B3471.8070209 at rejon.org>
> Content-Type: text/plain; charset=ISO-8859-1;
> format=flowed
>
> First of all thanks for your wonderful insight!
>
> Heiner Wolf wrote:
> > Hi,
> >
> >
> >>I interested to know if there are any good
> resources, documents, or
> >>source code I could look at to see how to properly
> receive
> >>packets from a jabber server like jabberd (which I
> am using) via TCP and
> >>then how to receive and reconstruct the entire
> packet.
> >
> >
> > When you deal with TCP as in the case of Jabber,
> then you must not think in terms of 'packets'. Both
> parties will receive a stream of bytes. While they
> send chunks of data on the connection, there is no
> guarantee that the receiver gets the data in the
> original chunks. The only guarantees that TCP gives
> are 1. that the data will arrive or you get an error
> 2. the byte order will be retained. Again: the
> receiver might get the data in totally different
> 'packets'.
> >
> >
> >>I'm using Visual Studio .net and WINSOCK to do
> connection and
> >>receiving. Right now I have a working client that
> receive packets that
> >>are 8129 bytes, but these packets might not
> contain the full message.
> >>This problem gets worse with more traffic.
> >
> >
> > What you must do is: forward every piece of data
> to the protocol parser. In this case it is an XML
> parser. The XML parser must be able to parse
> 'incomplete' XML and tell you about the structure
> before the main wrapper tag is closed. People call
> it a SAX parser as opposed to DOM parsers. You need
> a SAX parser. You feed it with every byte that comes
> from the connection. There is virtually nothing
> between the read() system call where you get data
> from the connection and the parse() where you
> forward the data to the parser. The parser will
> consume the bytes. The parser will tell you when a
> first order tag is finished. That would be something
> like a <message/> or <presence/> inside a
> <stream:stream>. If this happens then you can
> analyze the first order tag. That's then called a
> stanza in Jabber terms. In XML terms it is just the
> first order sub tag of the XML wrapper tag.
>
> What parser would you recommend? I'm looking into
> expat. I was using
> tinyXML, but it doesn't seem to fit the bill you are
> describing...
>
> >
> >
> >>What is the best way to construct entire jabber
> server packets into
> >>comlete packets/message. For example, the server
> might send a user's
> >>message in xml, and because of web traffic the
> complete message might
> >>not arrive in teh received 8192 bytes...
> >
> >
> > I reiterate, because this is important: this is
> TCP. There are no messages. Your network API will
> give you multiple bytes at once. This looks like a
> message. You don't care. You handle all data to the
> XML parser. The parser will tell you when stanzas
> are complete. You are probably testing in your lab.
> Over the wide internet you might even get smaller
> pieces of data at once (like 500 bytes). Stanzas
> might be split badly. There might be even the last
> '>' missing. Don't look at the data directly. Let
> the XML parser look. It will tell you when a stanza
> is complete.
> >
> >
> >>Other than this problem, my custom jabber client
> for this game,
> >>gopetslive.com is going pretty well.
> >>
> >>Any help or code sample or pointers would be much
> appreciated.
> >
> >
> > hw
> > --
> > Dr. Klaus H. Wolf
> > bluehands GmbH & Co.mmunication KG
> > http://www.bluehands.de/people/hw
> > +49 (0721) 16108 75
> > --
> > Jabber enabled Virtual Presence on the Web:
> http://www.lluna.de/
> > Open Source Future History:
> http://www.galactic-developments.com/
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mail.jabber.org/mailman/listinfo/jdev
> >
> >
>
> --
> Jon Phillips
>
> KOREA.PH.010.3140.7483
> USA.PH.858.361.2811
> jon at rejon.org
> http://www.rejon.org
>
> Inkscape (http://inkscape.org)
> Open Clip Art Library (www.openclipart.org)
> CVS Book (http://cvsbook.ucsd.edu)
> Scale Journal (http://scale.ucsd.edu)
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 05 Nov 2004 09:27:19 +0100
> From: aliban at gmx.net
> Subject: Re: [jdev] TLS negotiation
> To: Jabber software development list
> <jdev at jabber.org>
> Message-ID: <418B4777.29221.4570563 at localhost>
> Content-Type: text/plain; charset=US-ASCII
>
> Just go to jabber.org and get a working client lib
> for your
> programming language.
>
> many of them have enough documentation, too.
>
> for c++/win32 you might try mine... XCD
>
> Edrin
>
> On 4 Nov 2004 at 21:36, kavitha e wrote:
>
> >
> > Hi Kamran,
> >
> > I am new to this jabber, i am just going thru
> RFC's,i
> > cant help you, but i need your help if you dont
> mind.
> >
> > You said u have developed xmpp complient C/S
> > applications can you just tell me how to do that?
> >
> > I have to create an application to access jabber
> > server & its transports for MSN & Yahoo
> messengers.
> > More clearly, i need access the API provided by
> Jabber
> > server through xml protocols.
> >
> > Can you suggest me how to go about it? What are
> the
> > jabber servers i need to download? What are steps
> i
> > need to follow?
> >
> > Please help me...
> >
> > Thanks & Regards
> > Kavitha
> > --- Kamran Zafar <dearkami at yahoo.com> wrote:
> >
> > > Hi,
> > >
> > > I have developed a xmpp compliant client and
> server
> > > applications with most of the features.
> > >
> > > Now I want to give (client 2 server )TLS
> > > implementation in it.
> > >
> > > Please let me know what should i need to do in
> my
> > > existing coding in order to add this feature.
> > >
> > > Regards,
> > > Kamran
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Check out the new Yahoo! Front Page.
> > > www.yahoo.com
> > >
> > >
> > > _______________________________________________
> > > jdev mailing list
> > > jdev at jabber.org
> > > http://mail.jabber.org/mailman/listinfo/jdev
> > >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Check out the new Yahoo! Front Page.
> > www.yahoo.com
> >
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mail.jabber.org/mailman/listinfo/jdev
> >
>
>
>
>
> ------------------------------
>
> Message: 8
> Date: Fri, 05 Nov 2004 09:29:34 +0100
> From: aliban at gmx.net
> Subject: Re: [jdev] TCP Packet Construction
> To: Jabber software development list
> <jdev at jabber.org>
> Message-ID: <418B47FE.15003.4591528 at localhost>
> Content-Type: text/plain; charset=US-ASCII
>
> yes, expat is good.
>
> you may look in my code, i did it this way
> with
> winsock /vc++
> expat
>
> my source is under GPL! available at
> xcd.jabberstudio.org
>
> Edrin
>
> On 5 Nov 2004 at 17:06, Jon Phillips wrote:
>
> > First of all thanks for your wonderful insight!
> >
> > Heiner Wolf wrote:
> > > Hi,
> > >
> > >
> > >>I interested to know if there are any good
> resources, documents, or
> > >>source code I could look at to see how to
> properly receive
> > >>packets from a jabber server like jabberd (which
> I am using) via TCP and
> > >>then how to receive and reconstruct the entire
> packet.
> > >
> > >
> > > When you deal with TCP as in the case of Jabber,
> then you must not think in terms of 'packets'. Both
> parties will receive a stream of bytes. While they
> send chunks of data on the connection, there is no
> guarantee that the receiver gets the data in the
> original chunks. The only guarantees that TCP gives
> are 1. that the data will arrive or you get an error
> 2. the byte order will be retained. Again: the
> receiver might get the data in totally different
> 'packets'.
> > >
> > >
> > >>I'm using Visual Studio .net and WINSOCK to do
> connection and
> > >>receiving. Right now I have a working client
> that receive packets that
> > >>are 8129 bytes, but these packets might not
> contain the full message.
> > >>This problem gets worse with more traffic.
> > >
> > >
> > > What you must do is: forward every piece of data
> to the protocol parser. In this case it is an XML
> parser. The XML parser must be able to parse
> 'incomplete' XML and tell you about the structure
> before the main wrapper tag is closed. People call
> it a SAX parser as opposed to DOM parsers. You need
> a SAX parser. You feed it with every byte that comes
> from the connection. There is virtually nothing
> between the read() system call where you get data
> from the connection and the parse() where you
> forward the data to
> the parser. The parser will consume the bytes. The
> parser will tell you when a first order tag is
> finished. That would be something like a <message/>
> or <presence/> inside a <stream:stream>. If this
> happens then you can analyze the first order tag.
> That's then called a stanza in Jabber terms. In XML
> terms it is just the first order sub tag of the XML
> wrapper tag.
> >
> > What parser would you recommend? I'm looking into
> expat. I was using
> > tinyXML, but it doesn't seem to fit the bill you
> are describing...
> >
> > >
> > >
> > >>What is the best way to construct entire jabber
> server packets into
> > >>comlete packets/message. For example, the server
> might send a user's
> > >>message in xml, and because of web traffic the
> complete message might
> > >>not arrive in teh received 8192 bytes...
> > >
> > >
> > > I reiterate, because this is important: this is
> TCP. There are no messages. Your network API will
> give you multiple bytes at once. This looks like a
> message. You don't care. You handle all data to the
> XML parser. The parser will tell you when stanzas
> are complete. You are probably testing in your lab.
> Over the wide internet you might even get smaller
> pieces of data at once (like 500 bytes). Stanzas
> might be split badly. There might be even the last
> '>' missing. Don't look at the data directly. Let
> the XML
> parser look. It will tell you when a stanza is
> complete.
> > >
> > >
> > >>Other than this problem, my custom jabber client
> for this game,
> > >>gopetslive.com is going pretty well.
> > >>
> > >>Any help or code sample or pointers would be
> much appreciated.
> > >
> > >
> > > hw
> > > --
> > > Dr. Klaus H. Wolf
> > > bluehands GmbH & Co.mmunication KG
> > > http://www.bluehands.de/people/hw
> > > +49 (0721) 16108 75
> > > --
> > > Jabber enabled Virtual Presence on the Web:
> http://www.lluna.de/
> > > Open Source Future History:
> http://www.galactic-developments.com/
> > > _______________________________________________
> > > jdev mailing list
> > > jdev at jabber.org
> > > http://mail.jabber.org/mailman/listinfo/jdev
> > >
> > >
> >
> > --
> > Jon Phillips
> >
> > KOREA.PH.010.3140.7483
> > USA.PH.858.361.2811
> > jon at rejon.org
> > http://www.rejon.org
> >
> > Inkscape (http://inkscape.org)
> > Open Clip Art Library (www.openclipart.org)
> > CVS Book (http://cvsbook.ucsd.edu)
> > Scale Journal (http://scale.ucsd.edu)
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mail.jabber.org/mailman/listinfo/jdev
> >
>
>
>
>
> ------------------------------
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mail.jabber.org/mailman/listinfo/jdev
>
>
> End of jdev Digest, Vol 10, Issue 4
> ***********************************
>
__________________________________
Do you Yahoo!?
Check out the new Yahoo! Front Page.
www.yahoo.com
More information about the JDev
mailing list