[dev] Notification question

[Chuck Hagenbuch]

Quoting Hans Lellelid <hans at appliedsec.com>:

> The one question I had for this list is whether there is any design
> reason why $message in the $notification->push() method would need to be
> a string.  I would like to push an array -- e.g. with the thread_id that
> was updated etc. -- and while there doesn't seem to be anything in the
> Notification class that would prevent this, the assumption does seem to
> be that $message is a string -- and I'm wondering if there is any larger
> picture in Horde that I'm missing.  (I don't want to misuse the API so
> that my app would be incompatible w/ future releases.)

We'd have to modify the API so that the current listeners handle things
correctly, but I don't think that'd be a problem. In fact, I'd be in favor
of pushing around Notification_Event objects instead of strings, so that we
can have other kinds of info easily in there, and listeners can only take
what they want.

Do share the new listeners that you're working on with us!

-chuck

--
Charles Hagenbuch, <chuck at horde.org>
must ... find ... acorns ... *thud*