[Tickets #13231] Re: Hashtable session handler doesn't unlock on session close

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13231
------------------------------------------------------------------------------
  Ticket             | 13231
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Hashtable session handler doesn't unlock on session
                     | close
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-05-28 18:56) wrote:

Back to the initial topic of this ticket...

I remember somewhere bringing up exactly this issue ... that it didn't  
seem to make sense to issue X # of listEvents requests as opposed to  
packaging all of them together in a single call. (Can't find a ticket,  
and searching my e-mails didn't uncover anything either).

I remember being told at the time that this was necessary due to the  
way the javascript code was written.  Which didn't seem to be a  
satisfactory resolution, IMHO, since that responded only to why it  
wasn't currently being done as opposed to whether it was a good idea  
or not.

Still feel that this is a valid concern.