<[EMAIL PROTECTED]> wrote: > I think it should, as it signals changes in the storage. That is also > why it is called from the storage layer: only once the storage changes > is the call necessary. I don't agree, creating nofitications is not reserved to the storage. MMEvents for example creates nofitications when a start or stop time is reached (I don't know why).
- Re: HACK: multicast / unicast [ADDED VOTE] Pierre van Rooden
- Re: HACK: multicast / unicast [ADDED VOTE] Gerard van Enk
- Re: HACK: multicast / unicast [ADDED VOTE] Kees Jongenburger
- Re: HACK: multicast / unicast [ADDED V... Gerard van Enk
- Re: HACK: multicast / unicast [AD... Andr� van Toly
- Re: HACK: multicast / unicast... Gerard van Enk
- Re: HACK: multicast / unicast... Andr� van Toly
- Re: HACK: multicast / unicast [ADDED VOTE] Michiel Meeuwissen
- Re: HACK: multicast / unicast [ADDED VOTE] Kees Jongenburger
- Re: HACK: multicast / unicast [ADDED VOTE] Pierre van Rooden
- Re: HACK: multicast / unicast [ADDED VOTE... Kees Jongenburger
- Re: HACK: multicast / unicast [ADDED VOTE] Rico Jansen
- Re: HACK: multicast / unicast [ADDED VOTE] Pierre van Rooden
- Re: HACK: multicast / unicast [ADDED VOTE] Rico Jansen
- Re: HACK: multicast / unicast [ADDED VOTE] Michiel Meeuwissen
- Re: HACK: multicast / unicast [ADDED VOTE] Rico Jansen
- Re: HACK: multicast / unicast [ADDED VOTE] Jaco de Groot
- RE: HACK: multicast / unicast [ADDED VOTE] Nico Klasens
