On 19.04.12 18:19, Paul Clare wrote:
<< 1. If people are using BOSH, it probably means that Vysper is
embedded in their servlet application.
<< So the Bosh piece needs to be easily accessible to someone else's
servlet code. I'd like to move
<< towards implementing a 'Connection Manager' endpoint. This endpoint
would know how to
<< communication with the Vysper runtime, and also present an API that
servlets could use. I still think
<< Vysper would need to implement a reference servlet that uses this
connection manager. Other people
<< could then use that as an example of how to integrate it into their
servlet code.
A Connection Manager endpoint would be really, REALLY great.
What advantages would that have (beyond the obvious point of
de-colocating CM + XMPP)?
(Today, users could already use the BoshServlet and not instantiate
BoshEndpoint. Anyone doing this?)
AFAIK such connection managers are already available. Anyone tried one
of those? Why should we create our own impl?
In addition to some of the issues that we have already discussed there
is another that I have been working around over the past week.
XEP-0206 Section 7 Recipient-Unavailable
This is not implemented, I am not sure it was even considered.
It's helpfull to create JIRA issues to track things like that.
I opened VYSPER-308.
Bernd
