On 8/25/07, Mitch Stewart <[EMAIL PROTECTED]> wrote: > I'm going to answer my own question after fully reading your website. > > It DOES support XMPP over HTTP. :)
Well, "requests" over XMPP. It provides a way to make HTTP-like requests over XMPP. After forming the URI correctly, you can just use a Client instance to do gets, posts, etc. For servers, it lets you setup a service that receives over XMPP. Your restlet gets invoked just like it would over HTTP and the response gets send back over XMPP to the sender. The whole thing works async on the server side but the client can use the "sxeerkat" protocol to make an synchronous call. Otherwise, with the "xeerkat" protocol, responses are returned immediately with 200 status code if the message could be send. You then receive the response message asynchronously via a listener interface. When tunneling over XMPP to a server, the synchronous protocol is gong to be much more useful. In the case of P2P computing, handling responses asynchronously lets the sender continue to do useful work while waiting for the response. --Alex Milowski
