[Pidgin] #9015: Incorrect Implementation of XMPP Ping (was: 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 darkrain42):

  * status:  new => pending


Comment:

 My understanding is that the goal of the keepalive ping is to ensure that
 our connection to the server is still alive (and continues to stay alive,
 since intermediary network devices like NATs might time out the TCP
 connection if there is no traffic for some amount of time).

 The ping functions at a higher level than the TCP whitespace ping since it
 ensures not only that the TCP connection is still available but also that
 parts of server are still functioning properly since we get an
 application-level response, so I'd consider falling back to a whitespace
 ping to be less than ideal.

 In a quick skim of the [http://xmpp.org/extensions/xep-0199.html relevant
 XEP], I don't see anything that indicates an application MUST NOT send
 further pings if the response to a previous one is an error (or the server
 doesn't support the relevant namespace), so I don't believe the XMPP prpl
 is misusing the pings.

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