Hello On Sun, Sep 28, 2008 at 11:42:56PM -0700, Justin Karneges wrote: > On Sunday 28 September 2008 21:52:49 jlist wrote: > 2) Don't send TLS bytes into your SAX parser. When you receive > <proceed/>[binary data], then you want to make sure that [binary data] isn't > SAX-parsed. Unless your parser allows you to peek at unprocessed data, the > purest solution is to feed one byte at a time to the parser so that you can > manage an "unprocessed" data buffer yourself.
I tried to create my own XMPP parser/library (for, ehm, educational purposes). I never come across this issue. As far as I understand it, I get proceed, but no more binary data. I send binary data first (I initiate the SSL handshake), more come as a response and I can be ready then. So, when I receive proceed, take a stock standard SSL/TLS library, put it between the socket and new instance of the parser, everything works all by itself and the parser starts receiving data once encryption is negotiated. Or did I miss something important? It worked for me. Have a nice day -- I have a theory that it's impossible to prove anything, but I can't prove it. Michal 'vorner' Vaner
pgp4XLjgR0lKz.pgp
Description: PGP signature
_______________________________________________ JDev mailing list FAQ: http://www.jabber.org/discussion-lists/jdev-faq Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [EMAIL PROTECTED] _______________________________________________
