hi guys, i think it is confusing to deal with all those technologies for a newbie. everything from jackrabbit to sling to jcr to osgi to launchpad to ujax. some of this complexity is not necessary and can be removed easily. i think the ujax / sling distinction can definitely go. i would basically recommend to replace ujax with sling throughout the code, this particularly includes the js side, and would graduate ujax into the sling js library, which makes perfect sense to me.
regarding r-u-microjax, and related acronyms, this was more making fun of bad acronyms than anything else and i always hoped that someone would come along with a better name, so i am more than happy to just call it "sling". regards, david On Mon, Mar 10, 2008 at 8:09 PM, Tobias Bocanegra <[EMAIL PROTECTED]> wrote: > doesn't the "Jax" refer to the mechanism how the form post is handled? > it would at least call it 'sjax' > > regards, toby > > > > On 3/10/08, Felix Meschberger <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > Currently names used by Sling are prefixed with sling: with the > > exception of well known parameters of the ujax servlets. To get all > > these prefixes in line I suggest we change the prefix used by ujax > > parameters to sling: > > > > WDYT ? > > > > Regards > > > > Felix > > > > > > > -- > -----------------------------------------< [EMAIL PROTECTED] >--- > Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel > T +41 61 226 98 98, F +41 61 226 98 97 > -----------------------------------------------< http://www.day.com >--- >
