[Tickets #9017] Re: Ajax notifications too greedy

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9017
------------------------------------------------------------------------------
  Ticket             | 9017
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Ajax notifications too greedy
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 2. Medium
  Milestone          | 4.0
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2010-05-10 17:05) wrote:

The only practical way of doing this that I can see is to define, in  
each application's init() function, this pseudocode:

if ($GLOBALS['registry']->initialApp == CURRENT_APP) {
     $_SESSION['horde_notification']['override'] = ($is_ajax_view)
         ? Ajax_Display_Handler
         : null;
}

The better solution would be to abstract all notification code out of  
the framework libraries, create a Utility object that sits between the  
injector and the Notification library, and then have the initializing  
application doing something like:
$injector->getInstance('Horde_Notification')->setMode('ajax')

setMode() would do the necessary push/pop of the Notification handlers.