[ 
https://issues.apache.org/jira/browse/VYSPER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723013#action_12723013
 ] 

Niklas Gustavsson commented on VYSPER-12:
-----------------------------------------

Commited partial support (client->server pings only) in rev 787596. Let me know 
if things look alright. 

As for server->client (and in the future us->other-server), how about adding a 
SessionIdleHandler interface accessible via SessionContext. In the case of MINA 
detecting an idle session, it calls this where the default implementation can 
then ping the client. Should the ping not return within X seconds, we call 
SessionContext.endSession(). The last step though is a problem since there 
currently doesn't seem to be a way to really close the MINA session from the 
abstracted Vysper code (this is duly noted in AbstractSessionContext: "TODO 
close underlying transport")? How about overriding endSession in 
MinaBackedSessionContext?

Also, what is the best way for the server to send out a ping and then wait for 
a response?

> Implement XEP-0199: XMPP Ping
> -----------------------------
>
>                 Key: VYSPER-12
>                 URL: https://issues.apache.org/jira/browse/VYSPER-12
>             Project: VYSPER
>          Issue Type: Bug
>          Components: extension
>            Reporter: Bernd Fondermann
>
> XMPP Ping is a XMPP extension specified at 
> http://www.xmpp.org/extensions/xep-0199.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to