You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Bernd Fondermann (Created) (JIRA)" <ji...@apache.org> on 2012/04/19 20:26:39 UTC
[jira] [Created] (VYSPER-308) Implement BOSH XEP-0206 Section 7
Recipient-Unavailable
Implement BOSH XEP-0206 Section 7 Recipient-Unavailable
--------------------------------------------------------
Key: VYSPER-308
URL: https://issues.apache.org/jira/browse/VYSPER-308
Project: VYSPER
Issue Type: New Feature
Components: BOSH
Reporter: Bernd Fondermann
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VYSPER-308) Implement BOSH XEP-0206 Section 7
Recipient-Unavailable
Posted by "Bernd Fondermann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VYSPER-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bernd Fondermann updated VYSPER-308:
------------------------------------
Description:
from dev-ML:
> XEP-0206 Section 7 Recipient-Unavailable
>
> This is not implemented, I am not sure it was even considered.
>
> While looking into ways to implement this one thing became painfully
> obvious, using the StanzaWriter interface is an upstream dead end.
> (Which I suppose makes some sense if you are looking to decouple the CM
> from the XMPP core).
>
> When BoshBackedSessionContext.close is called the DelayedResponseQueue
> (Which is essentially the CM's buffer) needs to be drained and Message
> and certain IQs persisted.
>
> I implemented as much as I could filtering the stanzas in the DRQ and
> grabbing a handle to the OfflineStanzaReceiver (it's a little messy but
> it does work pretty well).
>
> The last part that I could not implement was the handling of persistence
> exceptions which should return an error back to the sender. I do not see
> a way to get back downstream to handle this unless the implementation is
> more in line with the core Endpoint and StanzaRelay implementations.
>
> -Paul
> Implement BOSH XEP-0206 Section 7 Recipient-Unavailable
> --------------------------------------------------------
>
> Key: VYSPER-308
> URL: https://issues.apache.org/jira/browse/VYSPER-308
> Project: VYSPER
> Issue Type: New Feature
> Components: BOSH
> Reporter: Bernd Fondermann
>
> from dev-ML:
> > XEP-0206 Section 7 Recipient-Unavailable
> >
> > This is not implemented, I am not sure it was even considered.
> >
> > While looking into ways to implement this one thing became painfully
> > obvious, using the StanzaWriter interface is an upstream dead end.
> > (Which I suppose makes some sense if you are looking to decouple the CM
> > from the XMPP core).
> >
> > When BoshBackedSessionContext.close is called the DelayedResponseQueue
> > (Which is essentially the CM's buffer) needs to be drained and Message
> > and certain IQs persisted.
> >
> > I implemented as much as I could filtering the stanzas in the DRQ and
> > grabbing a handle to the OfflineStanzaReceiver (it's a little messy but
> > it does work pretty well).
> >
> > The last part that I could not implement was the handling of persistence
> > exceptions which should return an error back to the sender. I do not see
> > a way to get back downstream to handle this unless the implementation is
> > more in line with the core Endpoint and StanzaRelay implementations.
> >
> > -Paul
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira