[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 Slusarz <slusarz 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 Slusarz <slusarz at horde.org> (2010-10-20 14:36) wrote:

> <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).

That's what is expected.  $events is an array of Event objects.  Thus  
it needs to be serialized to maintain the object.

Here's what my notification session entry looks like:
a:2:{i:0;O:30:"Horde_Core_Notification_Status":5:{s:12:"?*?_coreDict";O:25:"Horde_Translation_Gettext":2:{s:10:"?*?_domain";s:10:"Horde_Core";s:11:"?*?_gettext";b:1;}s:7:"charset";s:5:"UTF-8";s:7:"message";s:3:"foo";s:5:"flags";a:0:{}s:4:"type";s:12:"horde.notice";}i:1;O:30:"Horde_Core_Notification_Status":5:{s:12:"?*?_coreDict";O:25:"Horde_Translation_Gettext":2:{s:10:"?*?_domain";s:10:"Horde_Core";s:11:"?*?_gettext";b:1;}s:7:"charset";s:5:"UTF-8";s:7:"message";s:3:"foo";s:5:"flags";a:0:{}s:4:"type";s:12:"horde.notice";}}