[
https://issues.apache.org/jira/browse/VYSPER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723047#action_12723047
]
Bernd Fondermann commented on VYSPER-12:
----------------------------------------
+1 for SessionIdleHandler.
PING a client:
Please note that there are other means in XMPP to keep a session alive, for
example sending message stanzas with empty body. I don't know if this is a XEP,
too.
The client might not support this XEP, so closing the session must be handled
with care. The proper way to figure out if the client supports a certain
feature is via Entity Capabilities, which we currently don't support.
Session end:
The whole session ending part is an massive hole in the ground. This touches
the things you mentioned by also if the client sends a </stream:stream>.
There's a lot of work to be done, there. +1 for you proposals.
Wait for a response:
There is no response tracking on the server currently. I'd suggest a central
place where a callback can be registered to be called after a certain amount of
time.
Currently, AFAIK, we do not send IQ sets to the client, so this wasn't
neccessary yet.
> 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.
