[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:  enhancement  |      Status:  reopened                 
  Priority:  minor        |   Milestone:  2.1.1                    
 Component:  libpurple    |     Version:  2.1.0                    
Resolution:               |    Keywords:  direct IM AIM socket idle
   Pending:  0            |  
--------------------------+-------------------------------------------------
Comment (by MarkDoliner):

 I'm not sure what an empty ping would look like for a direct connection...

 The server ping is an empty channel 5 FLAP, but direct connections don't
 speak FLAP at all.  Personally I think it kind of makes sense for inactive
 direct connections to be closed.  I mean, if the firewall is timing out
 inactive connections, should we really try to circumvent that?

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