Niklas Gustavsson wrote:
On Sun, Nov 22, 2009 at 2:57 PM, Bernd Fondermann bf_...@brainlounge.de
wrote:
However, wearing my XMPP-shutter-glasses, I like to add that Vysper
itself would not profit from extending it to parse more XML. Vysper
needs fast fail, where any XML not supported by XMPP
there, I'm thinking of breaking out the XML parser in
Vysper into a separate module (still within the Vysper subproject, but
with it's own JAR). Thus, it would have no dependencies on Vysper. In
the long run, we might also provide a way to remove the current
limitations on what XML features
On Sun, Nov 22, 2009 at 2:57 PM, Bernd Fondermann bf_...@brainlounge.de wrote:
However, wearing my XMPP-shutter-glasses, I like to add that Vysper
itself would not profit from extending it to parse more XML. Vysper
needs fast fail, where any XML not supported by XMPP leads to an
immediate
Hi
Since there has been some interest here on using XML decoders with
MINA, and the inherit problems with doing this with the standard XML
parsers out there, I'm thinking of breaking out the XML parser in
Vysper into a separate module (still within the Vysper subproject, but
with it's own JAR
Niklas Gustavsson wrote:
Hi
Since there has been some interest here on using XML decoders with
MINA, and the inherit problems with doing this with the standard XML
parsers out there, I'm thinking of breaking out the XML parser in
Vysper into a separate module (still within the Vysper subproject
of breaking out the XML parser in
Vysper into a separate module (still within the Vysper subproject, but
with it's own JAR). Thus, it would have no dependencies on Vysper. In
the long run, we might also provide a way to remove the current
limitations on what XML features are supported
