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 filter is not a desirable scenario to me. Hence, I would really like to add this as a requirement/wish for sling/microsling/TWFKAU 2.0.
Cheers Michael PS: sorry, but: <rant> 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 (I just made up that number) and that scripting languages are often not type safe. But still, the web is full of extremely successful web technologies made with interpreted/scripted languages and extremely scaled web sites built upon them (e.g. Perl, ColdFusion, PHP, Rails, yScript and Yahoo, Facebook, Myspace respectively). So, in all seriousness, I do not at all agree with equating scripting and beginner/non-professional/unstructured. Moreover, I do not see scripting as an upgrade path to "the real thing". If we want to attract script developers to use sling to build web apps we should not think this way. To me, scripting is fine. </rant> On 12/21/07, Alexander Klimetschek <[EMAIL PROTECTED]> wrote: > > 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 implement a small filter that > > validates your request parameter or overrides the content-type- > > header in the response. > > [...] > > > Right. But moving to Sling, should mean chosing the Servlet > > implementation voluntarily over the script implementation. This > > separation between Sling and Microsling will not prove helpful if we > > do not understand that Servlet and scripts are two different, but > > equally valid expression of one of the concepts listed above. > > > > I agree that from the user point of view it makes sense to have > everything scriptable. Scripts directly in the repository are good for > the beginner, for quickly creating prototypes, for playing around with > certain features, for having a rapid application development platform > and even for being able to simply edit scripts in a browser-based IDE > like it is getting popular now (for the iPhone [1] or for web 2.0 apps > [2]). But once your application gets bigger, runs on multiple > machines, is developed by many developers at the same time and crossed > its first release, you need SCM, a structured deployment and software > lifecycle management. This is much better handled with OSGi bundles. > > 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 automatically create bundles from scripts inside the > repository, which would remove the burden of learning bundle > configuration from the user and give him a good kick start with his > existing code. This roundtrip feature would IMHO solve the script vs. > bundle discussion perfectly. > > Alex > > [1] http://www.jiggyapp.com/ > > [2] http://appjet.com/ > > > ----------------------------< [EMAIL PROTECTED] >--- > Alexander Klimetschek, Day Management AG, Barfuesserplatz 6, > CH - 4001 Basel, T +41 61 226 55 31, M +49 151 15 77 20 56 > ---------------------------------------< http://www.day.com >--- > > Xing: http://www.xing.com/go/invite/3268380.32d2d4 > LinkedIn: http://www.linkedin.com/in/klimetschek > Blog: http://weblogs.goshaky.com/weblogs/alexkli/ > > > > > > > > > > -- Michael Marth, http://dev.day.com
