[Standards] Network IO best practices
Cramer, E.R. (Eelco)
Eelco.Cramer at tno.nl
Mon Jun 11 09:14:46 UTC 2018
I’m also working on a project involving Go and XMPP but I’m creating a server component (XEP-0114). I’m reusing most of this project https://github.com/sheenobu/go-xco but I forked a fork of that project that adds some features (like asynchronous sending and receiving of messages). It works quite well for me and it might be helpful to you.
On 10 Jun 2018, at 16:10, Sam Whited <sam at samwhited.com<mailto:sam at samwhited.com>> wrote:
On Sun, Jun 10, 2018, at 00:09, Daniel Corbe wrote:
The chosen language here is Go and the few XMPP libraries that exist in our
world are hilariously incomplete. So I’m stuck implementing a library for
my application from scratch.
FWIW, I have an incomplete (though hopefully not hilariously so) XMPP implementation at https://godoc.org/mellium.im/xmpp that you can possibly reuse pieces of or use for inspiration. The JID implementation is complete and compliant to the best of my knowledge with RFC 7622. The main XMPP implementation doesn't currently have a good API for receiving and sending stanzas (so right now it's a bit of a manual process), so it's less useful but there are lots of other little child packages and lots of logic that might still be useful to you
Standards mailing list
Unsubscribe: Standards-unsubscribe at xmpp.org<mailto:Standards-unsubscribe at xmpp.org>
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Standards