I have a product I've created in .NET that a 3rd party company wants to take advantage of. My product revolves mostly around simple REST+JSON WebAPI's that I'm running in IIS.

This third party company has a messaging app and their own set of servers that communicate via XMPP. They want to be able to send and receive messages from me but require us to both receive and send via XMPP as well. AKA I have to figure out to do things their way so we can all play nice.

I've done some research and I'm trying to wrap my head around how to get started with XMPP. Documentation and support, for .NET at least, seems a bit lacking- including on this subreddit where searching "xmpp" net me 0 results. I have a few questions for anyone who knows anything about this:

 

1. Is a WebAPI project or even IIS in general a proper environment for an XMPP client/server or would I need to make a service, console app, winform, etc. to do this?

2. They say they are going to have their XMPP server "federate" to our XMPP server. Am I right in thinking that I essentially need to make my own XMPP server and then use that as a beacon to communicate with their server as well? I'm confused on how things should be structured. My only experience with "real time" communication is with signalR, where there is one "server" if you will, and all clients bind into it to relay information between each-other.

3. Is there a commonly used and well documented .NET library for this? I saw Jabber-Net but a bunch of the links to its documentation are broken and I'm not sure how supported or updated it is.