Hi Lars, That would be a cool idea.
It would probably be a good think for microsling and Sling to come up with a versatile, easy-to-use solution to use as a "default-servlet". Optimally, the solution would be able to support the microjax (or what was the name again ? :-) ) stuff as well as simple WebDAV for file-serve-like support. Not sure, whether this is possible though. Regards Felix Am Donnerstag, den 08.11.2007, 16:49 +0100 schrieb Lars Trieloff: > Hi Felix, > > microsling should provide the appropriate request handling and data > mapping for web forms 2.0 requests. Then you can develop rich web > applications very fast. > > I will provide a patch for handling this type of requests and will > build a small demo application to prove my thesis in the next days. > > Lars > > Am 05.11.2007 um 08:01 schrieb Felix Meschberger: > > > Hi Lars, > > > > Thanks for the information. > > > > Thinking about it, I am sure the Configuration Management Part of the > > Sling Web Console could definitely make use of this. But I am not > > sure, > > whether this should be part of microsling itself. > > > > Regards > > Felix > > > > Am Freitag, den 02.11.2007, 21:51 +0100 schrieb Lars Trieloff: > >>> > >>>> ...I think we should spend some time thinking about integrating > >>>> this Web > >>>> Forms 2.0 http://www.whatwg.org/specs/web-forms/current-work/ ... > >>> > >>> I'm not familiar with that spec, what does that imply, broadly > >>> speaking? > >> > >> > >> Having spent some hours discussing microjax with David today, I > >> decided to actually read the spec because I thought, I might be able > >> to learn something from the people who work at Apple, Mozilla and > >> Opera. And I did. > >> > >> Web Forms 2.0 have a number of implications that ease the development > >> of web applications by providing a powerful framework for client-side > >> validation and processing of web forms. This means: > >> - a validating type system for <input> elements, including date, > >> time, > >> e-mail-addresses, pattern maching, ranges, steps, sliders, etc > >> - an <output> element for outputting content (this is useful, hold > >> on) > >> - a repetition model for form elements including repeater templates, > >> add and delete row actions, min- and max-repeat specifications > >> - better handling of file uploads > >> - a powerful client side form events model including validation and > >> form processing > >> - form submission via POST, PUT, GET and DELETE > >> - form encodings that are encoding-aware and able to express order of > >> multi-value elements and repeaters > >> - fetching data from external files and pre-populating forms or > >> selection lists. Combine this with output fields and repeaters and > >> you > >> can fill any data into a form that can be expressed in a JCR node. > >> - more sophisticated ways of dealing with form responses, possible > >> actions are: doing nothing, loading another page or re-filling the > >> form with the response data. > >> > >> So there is a standards-compliant way of exchanging complex form data > >> between client and server and there is also a cross-browser > >> implementation available: http://code.google.com/p/webforms2/ > >> > >> I'm not sure how and if we could use this for microjax, but to me > >> this > >> looks like a solid basis to build webapps upon. > >> > >> Lars > >> -- > >> Lars Trieloff > >> [EMAIL PROTECTED] > >> http://weblogs.goshaky.com/weblogs/lars > >> > > > > -- > Lars Trieloff > [EMAIL PROTECTED] > http://weblogs.goshaky.com/weblogs/lars >
