[Pidgin] #9013: Change hardcoded CLOSE_CONV_TIMEOUT_SECS to user selected value

[Pidgin]

#9013: Change hardcoded CLOSE_CONV_TIMEOUT_SECS to user selected value
------------------------------------+---------------------------------------
 Reporter:  dlou99                  |        Owner:              
     Type:  patch                   |       Status:  pending     
Milestone:  Patches Needing Review  |    Component:  pidgin (gtk)
  Version:  2.5.5                   |   Resolution:              
 Keywords:                          |  
------------------------------------+---------------------------------------
Changes (by dlou99):

  * status:  pending => new


Comment:

 Replying to [comment:11 deryni]:
 > dlou99: You still haven't provided a reason why you want/need the
 timeout changed.

 Use case 1: User is a teacher and can only IM at the top of each hour for
 10 minutes.  User has a conversation with someone and 9mins, 58secs past
 the
 hour, says 'gotta go...bye.' and closes the window.  Just as the window
 closes,
 the person on the other end says 'by the way, remember that bla bla bla
 bla'.
 User sees the message just as the window closes but is only able to read
 the
 first half of the message.  Since class just started, user cannot re-open
 until 50 minutes later at the end of class.  Logging is turned off
 because user shares computer with another teacher.  Message is lost.
 Increasing close-timer to 55 minutes avoids lost message.

 Use case 2: User is conversing with a teacher (as above).  User asks
 teacher
 a question. Teacher is unable to respond immediately.  Teacher's computer
 idles and automatically goes to sleep, closing the connection.  User sees
 logout event and closes the conversation.  50 minutes later teacher wakes
 up
 computer, responds and shuts down.  If logging is turned off, user
 gets the answer with no context (i.e. user may have forgotten the
 question).
 Increasing close-timer to 55 minutes avoids lost context.

 Use case 3: Official Yahoo client has a "keep logs until program is
 closed"
 mode.  Setting a sufficiently long close-timer approximates this feature
 somewhat.  (yes, a plugin can be written to delete logs on quit signal but
 a long close-timer keeps everything in RAM while a plugin would need to
 do a messy secure delete to keep logs away from undelete utilities)

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