[Tickets #7422] Wrap long-running operations in session_write_close/session_start

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7422
------------------------------------------------------------------------------
  Ticket             | 7422
  Created By         | Chuck Hagenbuch <chuck at horde.org>
  Summary            | Wrap long-running operations in
                     | session_write_close/session_start
  Queue              | IMP
  Version            | HEAD
  Type               | Enhancement
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Horde Developers, Michael Slusarz, Chuck Hagenbuch
------------------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2008-10-01 16:52) wrote:

To avoid blocking operations in other tabs/browser windows, or in  
DIMP's case, simply other ajax requests, we should close the session  
(session_write_close) whenever possible before a long running  
operation. We do this some places, but haven't done it in others  
because of the need to update the session later. Turns out you can  
re-open the session by calling session_start (we'll probably need  
Horde::setupSessionHandler) again, as long as headers haven't been sent.

Especially with DIMP I think this would be useful to try. The thing I  
noticed locking on earlier that brought it to mind was emptying a  
large mailbox; DIMP generating a message list might be another. I'm  
sure there are more.