Tickets :: Comment on [#8023] New Horde

* Your Email Address
* Spam protection	Enter the letters below: . ..__ __ .___..__ \|__\|[__)/ ` \| [__) \| \|\| \__. \| [__)
Comment	>> Any time you try to do something in a second tab while a mailbox is > >> being filtered or emptied, for example. Or when the current sidebar > >> ajax reloads while another page is loading. And I expect all of this > >> to get more common with rich apps where ajax requests can fire from > >> different parts of the page. > > > > These are performance issues rather than race conditions though. I > can live with performance issues if using multiple different tabs. > The article linked to in this article mostly seems concerned with > race conditions. Since we do locking in our sessionhandlers, it does > not pertain to us. > > > >> As long as we have longer-running requests and/or large items in the > >> session, I think it's a good idea to be able to separate them. If we > >> use the session_write_close/session_open trick and stop storing > >> things like MIME objects in the session, then I can let it go. > > > > We don't store MIME objects in the session (not since the MIME > rewrite). In fact, the major culprit size-wise is registry data > (almost 35% of the session size) and cached prefs data. I've been > thinking about ways to remove the registry data for months now, since > 95% of the data in there is never used by the application in any > given session. In terms of improving session size, this is the place > to attack. I'll file another ticket for this issue.
Attachment
Watch this ticket

Saved Queries