sgissinger/jabbernet-2010

A VS2010 compliancy fork of jabber-net library aiming at supporting Jingle and Jingle ICE

jabbernet-2010's Issues

README lack

Please include "Solution items/README"

Does it support X-MESSENGER-OAUTH2 and X-FACEBOOK-PLATFORM Mechanisms?

Hi,
regards for the good work!
I have a question:
Is there any plan to add the following SASL mechanisms to the library?

X-MESSENGER-OAUTH2 ( for live messsenger OAuth authentication)
and X-FACEBOOK-PLATFORM ( for facebook OAuth authentication)

I think it could be a great improve to the library
thanks in advance

InvalidTokenException when intensive data exchange

When one client exchange data with approximately 500 clients consistently observed this exception. I can not understand whether it is in the library is something wrong, or Openfire sends bad packets.

Example data from log:

Recieved packet:

<iq type="r52ult" id="JN_555" from="plg">b.srv-wp" to="kropadmin@srv-wp/XPMUser"/><iq id="JN_309" type="set" from="35215401@srv-wp/client" to="kropadmin@srv-wp/XPMUser"ame>clientupdate_334_4.pack</papp:updat

Exception:

jabber.protocol.AsynchElementStream+XMLParseException: Parsing exception ---> OFFSET: 168 TYPE: 0 xpnet.InvalidTokenException: "xpnet.InvalidTokenException". в xpnet.Encoding.scanAtts(Int32 nameStart, Byte[] buf, Int32 off, Int32 end, ContentToken token) в xpnet.Encoding.scanLt(Byte[] buf, Int32 off, Int32 end, ContentToken token) в xpnet.Encoding.tokenizeContent(Byte[] buf, Int32 off, Int32 end, ContentToken token) в jabber.protocol.AsynchElementStream.Push(Byte[] buf, Int32 offset, Int32 length) в jabber.connection.SocketStanzaStream.bedrock.net.ISocketEventListener.OnRead(BaseSocket sock, Byte[] buf, Int32 offset, Int32 length)
Context:
Outer element: <iq from="plg" type="r52ult" id="JN_555">b.srv-wp" to="kropadmin@srv-wp/XPMUser"/&gt;</iq> New text (note: it's normal to see what looks like extra close tags here): <iq type="r52ult" id="JN_555" from="plg">b.srv-wp" to="kropadmin@srv-wp/XPMUser"/><iq id="JN_309" type="set" from="35215401@srv-wp/client" to="kropadmin@srv-wp/XPMUser"ame>clientupdate_334_4.pack</papp:updat

Сomments:

Where
'r52ult' should be 'result',
'from="plg">b.srv-wp' should be 'from="pubsub.srv-wp'
'to="kropadmin@srv-wp/XPMUser"' should be 'to="kropadmin@srv-wp/User"',
also strange 'ame' and strfnge ending of packet '</papp:updat'