| Summary | Wrap long-running operations in session_write_close/session_start |
| Queue | IMP |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Assigned |
| Priority | 1. Low |
| Owners | Horde Developers, Michael Slusarz <slusarz (at) horde (dot) org>, Chuck Hagenbuch <chuck (at) horde (dot) org> |
| Requester | Chuck Hagenbuch <chuck (at) horde (dot) org> |
| Created | 10/01/2008 (276 days ago) |
| Due | |
| Updated | |
| Assigned | |
| Resolved | |
| Attachments | |
| Milestone | |
| Patch | No |
Patch ⇒
Milestone ⇒
Assigned to
Assigned to Michael Slusarz
Assigned to Chuck Hagenbuch
Summary ⇒ Wrap long-running operations in session_write_close/session_start
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ Assigned
Queue ⇒ IMP
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.