You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I see send and recieve ping message abilities themselves are implemented. But currently client part completely lacks support for periodic sending procedure that is required for complete implementation of XEP-0199. I mean 4.2 section - Client 2 Server pings.
XEP-0199 is optional by standard which means that server can omit support of this xep, but in practice I never saw such a server in a wild - most of them require pings or after some period of inactivity server closes connection. (Which is annoyng if you client sitting there for some notable period of time, eg it is bot.)
So having full support of XEP-0199 directly built-in to NewClient() is quite helpful (ofcorse there must be a option to toggle this feature).
The text was updated successfully, but these errors were encountered:
As far as I see send and recieve ping message abilities themselves are implemented. But currently client part completely lacks support for periodic sending procedure that is required for complete implementation of XEP-0199. I mean 4.2 section - Client 2 Server pings.
XEP-0199 is optional by standard which means that server can omit support of this xep, but in practice I never saw such a server in a wild - most of them require pings or after some period of inactivity server closes connection. (Which is annoyng if you client sitting there for some notable period of time, eg it is bot.)
So having full support of XEP-0199 directly built-in to NewClient() is quite helpful (ofcorse there must be a option to toggle this feature).
The text was updated successfully, but these errors were encountered: