Tickets :: Comment on [#10615] Locks on initial imp ajax requests

* Your Email Address
* Spam protection	Enter the letters below: .__ . ..__ .___..___. [__)\ /\| \ \| \| \| \ \/ \|__/ \| \|
Comment	>> What i discovered is that viewPort has the lock on the session and >> releases it when there's a potential long running operation. >> Meanwhile, listMailboxes starts executing (because it grabbed the >> lock on the session), and immediately releases the lock to supposedly >> perform a long running operation... >> The problem is that as far as i could test, the supposedly long run >> operation of listMailbox is not long, so it grabs the lock again >> (before viewPort does), and then it actually runs a potentially long >> operation (grabbing the list of all the mailboxes from imap, since >> this is not cachable).. > > This is incorrect. listMailboxes() does all IMAP calls related to > querying the mailbox tree when the session lock has been released. > By the time the session has been re-locked, there should be very > little (if anything) left to be done on the server (either PHP or > IMAP). > > That being said... looks like there is a mistake in listMailboxes(). > We are creating the IMP_Imap_Tree object before locking the session. > If this is the first time we have created the object, init() is > automatically called. So we are doing the mailbox listing before we > even close the session. This needs to be (and should now be) fixed. > . >> From what i've seen if you completely remove the lock releases from >> both requests, than viewPort will render much faster, and the user >> will only notice the loading on the folders sidebar. > > This is incorrect. At least one of these processes is blocking the > other - so there's no way it can be faster.
Attachment
Watch this ticket

Saved Queries