[
https://issues.apache.org/jira/browse/VYSPER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723051#action_12723051
]
Niklas Gustavsson commented on VYSPER-12:
-----------------------------------------
> 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.
Even if the client does not support pings, it should send an error response to
the iq we sent (at least that's what RFC 3920 and XEP-0199 suggests). We could
probably treat that as a pong.
> 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>.
How is </stream:stream> currently handled? Maybe we should turn this into a
JIRA issue on its own?
> 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.
