Tickets :: Comment on [#5108] session table deadlock with remote calendars

* Your Email Address
* Spam protection	Enter the letters below: . ..__ ..__ .__ \|__\|[__) \|[ __[__) \| \|\| \__\|[_./[__)
Comment	>> Actually, why is the page fetching the remote calendar still holding >> a lock on the > >> session table at this point anyways? > > > > A simple answer is that we use the session to cache results of remote > calendar lookups. A more complicated answer is that we do a _lot_ of > caching in the session, and it'd take a lot of careful work to make > sure that we do everything we need to the session, including all > possible preferences changes, then close the session (or write close, > anyway), and only then list events. > > > > Jan, do you remember what about remote calendars needs a session in > ics.php? If we can't fix that, either we can do that work to close > the session before listing events, we can try to recognize shares on > the same server and translate them internally. If I understand the > problem right we can't really pin this on table-level locking since > at best a user would still be able to lock their own session up, > right?
Attachment
Watch this ticket