Re: Event Scripting (was: Filter Scripting (was: POSTs and microjax))

2007-12-21 Thread Felix Meschberger
Hi Lars, Am Freitag, den 21.12.2007, 16:29 +0100 schrieb Lars Trieloff: > Hi Felix, > > I've been thinking about this, but do not see a solution right now. > The problem with the approach of executing the script with permissions > of the script owner (whoever this might be) is that in order t

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Michael Marth
Alex, I can understand both sides of the discussion because both are needed. > It just depends on the user's or customer's requirements. > > I agree. Maybe it'd be good if we treated scripting and Java development as equal citizens, i.e. if we tried to make available all features to both approach

Re: Event Scripting (was: Filter Scripting (was: POSTs and microjax))

2007-12-21 Thread Lars Trieloff
Hi Felix, I've been thinking about this, but do not see a solution right now. The problem with the approach of executing the script with permissions of the script owner (whoever this might be) is that in order to be able to observe the whole repository, we have to give read access to the

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Alexander Klimetschek
Hi Michael, Am 21.12.2007 um 14:58 schrieb Michael Marth: Regarding the sentiment that scripted web apps are "for beginners", do not support a structured deployment or development process and do not perform well: yes, it is true that compiled code runs 1000x faster than interpreted code

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Michael Marth
Guys, just like Lars I find that having "everything" scriptable is very desirable. "Everything" meaning in descending order of importance: render scripts, filters, event listeners. Building a web app where I start with some render scripts in Javascript but have to revert to Java for writing a filt

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Lars Trieloff
Hi Alex, It will be a great overall feature of Sling to support both "programming" styles. The only thing missing in the current state is support for an easy transition from your prototypical script-based application to a mainly servlet-based and bundled app. There is the idea to automati

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Alexander Klimetschek
Hi, Am 21.12.2007 um 12:46 schrieb Lars Trieloff: Right. But this realization should come from the user, not from the framework that says for this certain feature, you have to forget everything you learned about scripting and start using an IDE, Maven and OSGi, even if you just want to imp

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Felix Meschberger
Hi Lars, Am Freitag, den 21.12.2007, 14:02 +0100 schrieb Lars Trieloff: > Hi Felix, > > I think, we should protect the ability to install scripts or event > listeners, not limit the power of scripts or event listeners. You > could rephrase this example: Suppose somebody installs a GET.js scri

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Lars Trieloff
Hi Felix, I think, we should protect the ability to install scripts or event listeners, not limit the power of scripts or event listeners. You could rephrase this example: Suppose somebody installs a GET.js script with bad-side effects and tricks the administrator or power-user into reque

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Felix Meschberger
Hi Lars, Am Freitag, den 21.12.2007, 13:35 +0100 schrieb Lars Trieloff: > >> The event is executed with the credentials of Event.getUserId(). > > > > First it might not work. Of course, given the admin session, you might > > create a session of the desired user. Second, and more important: the > >

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Lars Trieloff
Hi Felix, The event is executed with the credentials of Event.getUserId(). First it might not work. Of course, given the admin session, you might create a session of the desired user. Second, and more important: the Event.getUserId is the user name of the session which performed the changes

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Felix Meschberger
Hi Lars, Am Freitag, den 21.12.2007, 12:46 +0100 schrieb Lars Trieloff: > > 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 ma

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Lars Trieloff
Hi Felix, - request handling - error handling We have both, right ? Right. And this is great. - 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-

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread Felix Meschberger
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 ? > -

Re: Filter Scripting (was: POSTs and microjax)

2007-12-21 Thread 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 - request filtering - response filtering - repository events - timed events (cron jobs) are scriptable. I think