Thanks Joe, that's what I thought. My problem is that I'm working on a scalable Jabber server implementation. I need to have a large number of Jabber connections handled by a small number of threads. The Jabber protocol represents an entire persistant connection as a single xml document with each message being an element child of the document. I think that I'm going to need a parser instance per connection, but I need all those parsers to be able to run in response to input on their associated channel.
If I wrote an asynchronous xml scanner, would I be able to plug this into the Xerces framework to avoid having to duplicate the different validation steps? It doesn't look like I want to implement XMLDocumentSource, as it assumes synchronous or pull parsing. Where would be a good place to start? Thanks! > -----Original Message----- > From: Joseph Kesselman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 25, 2002 6:18 AM > To: [EMAIL PROTECTED] > Subject: Re: Application Driven Parsing > > I don't think there's any way to run Xerces purely as a pipeline at this > time, unless I missed an announcement. > > The easiest solution would be to plug an "identity filter" stage into your > text pipeline, providing blocking for the parser's reads and (if > necessary) for the text source's writes... but that does require that the > code generating the text and the parser run in separate threads. > > __________________________________ > Joe Kesselman / IBM Research --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
