Hi,

Am Mittwoch, den 21.11.2007, 10:06 +0100 schrieb Michael Marth:
> That would be really cool. There is also a quite compelling real-world use
> case for this: in a lot of web apps emails need to be sent. Rather than
> having to send the email during the request-response cycle (and thus slowing
> down the response) an observer on the data could send it . This would make
> for a much nicer architecture because async operations (like mail) are
> really handled in an async way.

I agree, that there is a requirement for asynchronous follow-up
operations, notificiations of all sorts are probably most prominent.
Yet, these are application level and should probably be done on
application level - the Sling event bundle provides a great basis for
such things.

And yes, I am one of those few JCR users who insist on keeping stuff at
the application level which belongs to the application level and not
have the repo do things, just because the JCR allows it :-) For example,
the JCR events are very, very fine-grained and really hard to turn into
application level events.

Nevertheless, scripted event handling still sounds interesting ...

Regards
Felix

Reply via email to