On Mon, Apr 19, 2010 at 11:49 AM, Bernd Fondermann <[email protected]> wrote: >> To me (given finite resources), I think in-process (that is, in >> Vyspers process) is the most interesting option for us right now. This >> is where a Vysper implementation of BOSH can add some value. > > Vysper is designed to be embedded easily, for example in a DI-container > environment or a Tomcat, a Jetty etc. You could say this is still > in-process, and it is, but the container might already have bound HTTP > ports.
Agreed, but would you think this use case would be common enough to make it worth implementing? Servlets are not the perfect environment for long lived HTTP connections. Besides, isn't this what we got XEP-0156 to solve for us? >> For the >> separate process, there are already generic BOSH gateways out there. > > Which? JabberHTTPBind isn't. I didn't look into > http://kenai.com/projects/jbosh/pages/Home > but it seems it isn't, too. > > But what I really like to see is a solution which is capable of blending > into a servlet engine, e.g. does not re-implement HTTP, but rather is a > Servlet. Right, I assumed we were talking about a generic BOSH gateway. > I'm ok with separating processes later, but designing with that in mind. Fair enough. /niklas
