Hi Lars, Am Freitag, den 21.12.2007, 11:51 +0100 schrieb Lars Trieloff: > Hi Michael, Felix, > > I think what Michael needs when he refers to Microsling is a > scriptable Sling. This means that all the core aspects of Sling: > > - request handling > - error handling
We have both, right ? > - request filtering > - response filtering There is no difference in request and response filter - there is just filtering. Currently we implement this by requiring the registration of request-level or resource-level filters. The problem with filtering is, that it imposes certain performance degradation. So if you (or Michael) would be able to present a conceptor even a patch, we may certainly further discuss. > - repository events This sounds, easy to implement, though there are certain ACL related open issues: What credentials are active for the scripted events ? Who is allowed to post scripted JCR event handlers ? In fact this has already been discussed [1] to a certain degree but without reaching a final target... > - timed events (cron jobs) Carsten ? > are scriptable. I think this is a reasonable request and would allow > users to build powerful web applications in the script language (or > even servlets) they prefer. Well, I think, there are things, for which scripting is very well suited - such as processing GET requests - and other things where scripts are not actually adequate. So to build powerful applications, scripting may certainly be used, but over time, you may realize, that the scripting language of your choice might simply not be adequate. And to just use scripting, because for a given limited tool it is the only way to "extend" it, is probably not right solution. I would suggest to move to Sling in this case. Just my very personal €0.02. Regards Felix [1] http://www.mail-archive.com/sling-dev@incubator.apache.org/msg00948.html
