[Tickets #9324] Re: Horde_Session vs Horde_Notification

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9324
------------------------------------------------------------------------------
  Ticket             | 9324
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Horde_Session vs Horde_Notification
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2010-10-20 14:22) wrote:

> This is *exactly* what the code in  
> Horde_Core_Notification_Storage_Session is designed to prevent:
>
> line 59: $session['horde:notify/' . $listener . ';object'] = $events;
>
> This tells the session handler to force save this entry as an object  
> (using serialization) rather than doing type checking (which would  
> return array which would cause it to be json encoded).  This is  
> probably a good place to start debugging- it works perfectly for me  
> here.
>

dumping $_SESSION shows that it is indeed serialized, but the problem  
is, it's serializing an array, not an object:

<code>
         $events = $session['horde:notify/' . $listener . ';array'];
         $events[] = $event;
         $session['horde:notify/' . $listener . ';object'] = $events;
</code>

The entity being serialized is the array returned from the first  
assignment (and appended to on the second line).