[dev] Notification_Event first run

[Hans Lellelid]

Ha, yes!  I thought about serialization, figured that PHP could handle 
it natively, but you're absolutely right about the need to load all the 
event classes before session_start().   Thanks for taking care of this!

I keep thinking about the event/listener system.  I'd love to be able to 
target events to specified applications which have registered themselves 
as listeners / handlers for certain event types.  Anyway, I'll continue 
to think more about this.  This new system of passing an event object 
provides the flexibility to really push the notification system to new uses.

Thanks,
Hans

Chuck Hagenbuch wrote:

>Quoting Hans Lellelid <hans at appliedsec.com>:
>
>  
>
>>Here's another (more cleaned-up) version of the Notification_Event class
>>for
>>	horde/lib/Notification/Event.php
>>I'm also including the diffs for the Notification,
>>Notification_Listener_status, and Notification_Listener_status_kronolith
>>classes.
>>    
>>
>
>This got a little more complicated than your initial code because of the
>need to serialize objects before tossing them into the session; otherwise,
>the automatic deserialize when we start the session would create broken
>objects unless we loaded Notification_Event - and every possible subclass -
>before the first session_start().
>
>Now, Notification_Event is loaded transparently on demand, and you'll just
>have to make sure that any subclasses of Notification_Event() are loaded
>before you call $notification->notify().
>
>Thanks!
>
>-chuck
>
>--
>Charles Hagenbuch, <chuck at horde.org>
>must ... find ... acorns ... *thud*
>
>  
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4461 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.horde.org/archives/dev/attachments/20030116/28056459/smime.bin