[Pidgin] #2390: Direct IM (AIM) connection results in socket error if left idle and messages are dropped

[Pidgin]

#2390: Direct IM (AIM) connection results in socket error if left idle and
messages are dropped
------------------------+---------------------------------------------------
  Reporter:  Januschan  |       Owner:  MarkDoliner              
      Type:  defect     |      Status:  assigned                 
  Priority:  minor      |   Milestone:                           
 Component:  libpurple  |     Version:  2.1.0                    
Resolution:             |    Keywords:  direct IM AIM socket idle
   Pending:  1          |  
------------------------+---------------------------------------------------
Changes (by Januschan):

  * pending:  1 => 0

Comment:

 I apologize but when I initially opened this bug, I reported the incorrect
 version number.  I was using 2.02 and not 2.10.  I have since upgraded to
 2.10 and this issue is no longer reproducible.

 when trying to isolate this further, in either build I would see the same
 two error message scenarios.  If I am the one to establish the direct
 connection, after timeout I would see:

 Lost connection with the remote user: Windows socket error #10054

 If the remote user was the one to establish the connection, I would
 instead see:

 The remote user has closed the connection.

 In 2.02 the socket would be broken after either message, but this seems to
 no longer be the case.

 Thank you for investigating this!

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