[Pidgin] #9015: Incorrect Implementation of XMPP Ping

[Pidgin]

#9015: Incorrect Implementation of XMPP Ping
-------------------------+--------------------------------------------------
 Reporter:  niraj19july  |        Owner:  deryni 
     Type:  defect       |       Status:  pending
Milestone:               |    Component:  XMPP   
  Version:  2.5.5        |   Resolution:         
 Keywords:               |  
-------------------------+--------------------------------------------------
Changes (by niraj19july):

  * status:  pending => new


Comment:

 I am saying that TCP keep alive should be used only if server doesn't
 support the ping-pong protocol. I am not saying that you should use TCP
 keep alive with servers which support ping-pong protocol.

 As per XEP, during the Service Discovery server MUST report the fact that
 it supports XMPP Ping.

 If a client doesn't find the support of XMPP Ping from server during
 Service Discovery, client should not even try to ping the server.

 The problem with the current approach of Pidgin that it is assuming that
 all the xmpp servers are supporting xep-0199. It is wrong to make such
 assumptions and Service Discovery is meant for exactly the same reason.

 If a server is not supporting xmpp ping, how can error response be
 considered as pong from the server?

 Further, how can Pidgin force all the xmpp servers to support XEP-0199? I
 don't see any other xmpp client except Pidgin forcing this requirement on
 the server.

 I feel Pidgin must provide a way to disable these pings in case server
 doesn't support xep 0199.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9015#comment:3>
Pidgin <http://pidgin.im>
Pidgin