On Sun, Apr 18, 2010 at 10:33 PM, Bernd Fondermann
<[email protected]> wrote:
> I don't fully understand that plan.
> Especially the term 'Session' is missing here for me. Client-side
> stanzas are processed in the context of a session.

The session would give the session context for the stanza processor as
it's done now in Vysper (stored as an IoSession attribute).

> I didn't check with AsyncWeb, but I guess the patch copies its source
> code over to Vysper? I don't see a point in doing so. Why not create a
> dependency on the AsyncWeb library?

You are right here. I did not think at this possibility, I was
thinking of custom tailoring just the decoders/encoders for our own
purposes.
If we use an external binary library then I think there is no direct
advantage of using AsyncWeb (being MINA based)
and Jetty (or other HTTP servers) could be just as good for HTTP handling.

> Say you have a webserver already running on your vysper.org machine.
> Then you'd probably want that process to handle the HTTP-side of BOSH,
> too. So we need two basic modes of operation - in-process and separate
> processes.

For the separate processes, if you think of integration with Servlet
containers (Tomcat), then the Vysper Bosh endpoint would have to
implement servlet API, what do you think if this will be another
Vysper endpoint. Who will want to use Servlet containers could plug
that endpoint, and who will want a full Bosh XMPP server will use just
Vysper.

> You draw above: "stanza creation --> Bosh IoHandler"
> I don't understand that. Do you mean SessionContext?

I meant (assumed without drawing it) that the session context is
extracted (as is now in Vysper) from the IoSession in the
IoHandler#messageReceived()
My encoding scheme was more concerned how the parsing is done until it
reaches the Bosh IoHandler.

> I'd like us to evaluate Jetty, too. It's properly maintained and it
> implements the most recent standards in async web processing. WDYT?

I agree, initially I inclined towards AsyncWeb because it is MINA
based and because we're using the same mailing list :)

Bogdan

Reply via email to