You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Christophe Lombart <ch...@gmail.com> on 2007/11/01 09:18:09 UTC
Re: [RT] microsling ajax client
+1. Great idea.
On 10/31/07, Lars Trieloff <la...@trieloff.net> wrote:
>
>
> What about adding this as a default handler for the json extension,
> compared to an XML serialization as a default handler for the xml
> extension. (I am still thinking about adding a certain XML-processing
> framework as a very powerful script engine to Sling)
or use the current behaviour for a "debug" extension.
Christophe
Re: [RT] microsling ajax client
Posted by David Nuescheler <da...@day.com>.
> > We could use microjax as a nickname maybe.
how about "slingjax".
regards,
david
Re: [RT] microsling ajax client
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 11/1/07, Lars Trieloff <la...@trieloff.net> wrote:
> ...I know how much we all value these discussions, but as RJAX is taken
> and a really bad acronym and microajax is already taken by another
> framework, what about using
>
> AJACs - Asynchronous Javascript and Content....
don't like that, the sounds is the same as the real Ajax.
Note that my proposal was not microajax, it was microjax, which does
not seem to be used by other software.
-Bertrand
Re: [RT] microsling ajax client
Posted by Lars Trieloff <la...@trieloff.net>.
I know how much we all value these discussions, but as RJAX is taken
and a really bad acronym and microajax is already taken by another
framework, what about using
AJACs - Asynchronous Javascript and Content.
The trailing S stands for Sling (of couse) and it makes the word
almost sound like AJAX.
Lars
Am 01.11.2007 um 09:55 schrieb Bertrand Delacretaz:
> On 11/1/07, Michael Marth <mm...@day.com> wrote:
>
>> One comment: if we package "microsling Ajax client" (can we find
>> another
>> name, please?) ...
>
> no, no, not names again...aaaaarrghhhhhhhh......please....... ;-)
>
> We could use microjax as a nickname maybe.
--
Lars Trieloff
lars@trieloff.net
http://weblogs.goshaky.com/weblogs/lars
Re: [RT] microsling ajax client
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 11/1/07, Michael Marth <mm...@day.com> wrote:
> One comment: if we package "microsling Ajax client" (can we find another
> name, please?) ...
no, no, not names again...aaaaarrghhhhhhhh......please....... ;-)
We could use microjax as a nickname maybe.
> ...with microsling it makes even more sense to have esp as the
> default scripting language (the app developer needs to think in only one
> language - be it on the server or on the client)...
Sure, having javascript on both ends is cool.
-Bertrand
Re: [RT] microsling ajax client
Posted by Lars Trieloff <la...@trieloff.net>.
Is there a client-side ESP implementation? This would make it even
cooler: Using Javascript client-side and server-side, with ESP as
templating mechanism and the same JSON-to-JCR-mapping in both tiers
can speed up training and development dramatically.
Lars
Am 01.11.2007 um 09:48 schrieb Michael Marth:
> Nice idea.
>
> One comment: if we package "microsling Ajax client" (can we find
> another
> name, please?) with microsling it makes even more sense to have esp
> as the
> default scripting language (the app developer needs to think in only
> one
> language - be it on the server or on the client)
--
Lars Trieloff
lars@trieloff.net
http://weblogs.goshaky.com/weblogs/lars
Re: [RT] microsling ajax client
Posted by Michael Marth <mm...@day.com>.
Nice idea.
One comment: if we package "microsling Ajax client" (can we find another
name, please?) with microsling it makes even more sense to have esp as the
default scripting language (the app developer needs to think in only one
language - be it on the server or on the client)
Michael
On 11/1/07, Christophe Lombart <ch...@gmail.com> wrote:
>
> +1. Great idea.
>
> On 10/31/07, Lars Trieloff <la...@trieloff.net> wrote:
> >
> >
> > What about adding this as a default handler for the json extension,
> > compared to an XML serialization as a default handler for the xml
> > extension. (I am still thinking about adding a certain XML-processing
> > framework as a very powerful script engine to Sling)
>
>
> or use the current behaviour for a "debug" extension.
>
> Christophe
>