I'm not sure what architecture you are using, but aren't you doing something like: - read socket (TLS is handled at the socket layer) - unwrap sasl if sasl has been negotiated - uncompress if XEP-0138 compression has been negotiated - present ascii XML to XML parser I also don't see why you can't just keep doing what you are doing now (throwing out the parser). The only thing that is changing is the removal of the <stream:stream> stanzas. You can still throw away (or reset) the parser at the right moments.
> From: [EMAIL PROTECTED]> To: [email protected]> Date: Wed, 7 May 2008 > 21:42:02 -0600> Subject: Re: [Standards] stream restarts> > > "Simply" inserting a TLS wrap/unwrap stage is trivial to do with the > > > expat C API. However, it's incredibly complex with the vast majority > of > > XML parsers. For these, it's pretty easy to stop the current > processing, > > throw out the previous parser, and create a new parser > with the TLS > > and/or SASL unwrap next in the I/O stack.> > --> Matthew A. Miller> [EMAIL > > PROTECTED] _________________________________________________________________ With Windows Live for mobile, your contacts travel with you. http://www.windowslive.com/mobile/overview.html?ocid=TXT_TAGLM_WL_Refresh_mobile_052008
