On Sat, Apr 17, 2010 at 23:08, Bogdan Pistol (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/VYSPER-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12858184#action_12858184 > ] > > Bogdan Pistol commented on VYSPER-189: > -------------------------------------- > > The right place for a discussion is on jira or on the mailing list?
Depends. At least for more general discussions, the mailing list is better. > In my view the decoder could be like: > > raw bytes --> AsyncWeb decoder --> XML extraction --> stanza creation --> > Bosh IoHandler > > and the encoder: > > stanza --> XML serialization --> AsyncWeb encoder --> raw bytes > > The Bosh IoHandler could work with a Bosh StanzaProcessor that would > eventually process with some Bosh StanzaHandlers the stanzas and then it will > send the processed (as defined by XEP-0206) stanzas to the XMPP > StanzaProcessor. > > What do you think? 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. 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? 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. You draw above: "stanza creation --> Bosh IoHandler" I don't understand that. Do you mean SessionContext? I'd like us to evaluate Jetty, too. It's properly maintained and it implements the most recent standards in async web processing. WDYT? Bernd
