If there are .NET/Mono libraries available, that should work. Keep in mind, however, that - if you are building Web players - this will very likely make the Web player quite a bit larger since the assemblies need to be included (and it's very likely that these assemblies have dependencies to standard assemblies that then also need to be included).
For standalones, that shouldn't be much of an issue - but for Web players, it might be.
You could probably use one of the libraries listed here: XMPP Software: Libraries
Regarding the issue with Web players I've mentioned, read this for more details: Reducing included dlls in the Web Player (you'll need to scroll down to the bottom of the page).
answered Dec 10 '09 at 04:37 PM
I am looking at using XMPP for networking in Unity3d myself. No roadblocks so far, but I've only spent 8hrs looking into it all.
The Jabber-net assemblies add 860KB, which is almost trivial. You'd have some cost if you did it all yourself anyway.
As noted above, there may be dependencies that have to be added to a unity web-player build. I'll know more soon as I develop the idea further. But the references for the core Jabber-net assembly are the core ones plus System.XML and System.Security which should not need to be bundled.
As a side-question: is there a way for a web-player deploy to check what is available locally before sending assemblies? Perhaps a bootstrap process that creates a manifest is required.
answered Jan 11 '10 at 10:47 AM
Should be good; be sure to only include client libraries (some implementations include both the client and server, which would be a lot bigger). We use the SmartFoxServer library, which is basically a XMPPish chat server + stuff. It's C# library just starts up a new thread to handle the server socket, and then has a "poll" function for you to call in FixedUpdate() which locks a "event queue" mutex, enqueues new events from the server on the main thread, and then unlocks the mutex so both threads can go merrily on their way.
answered Jan 07 '10 at 08:11 PM
xian1971 whats your status on this ? I was not able to get jabber-net working in webplayer build, while it works fine in standalone builds. I guess this is due to security stuff in the webplayer and jabber-net uses some .NET libs which are not allowed there. what a bummer, XMPP would habe been perfect for my chatting stuff and presence etc.
answered Feb 18 '10 at 06:44 AM