AJAX is an acronym for Asynchronous Javascript and XML.  The idea is that
instead of submitting a request to a remote process (CGI script, Java
Servlet, etc) and displaying the results as a new page, you send an
asynchronous request to an XML resource, using the HttpXMLRequest object,
in response to user events, and use DOM to update the current page.  This
allows you to use information from the server (for example to validate user
input or to tailor the user interface).  Because the requests are sent
asynchronously, the user never leaves the current page, thereby maintaining
the illusion that everything is happening on the client side.

AdaptivePath, who coined the term, has an introductory article on their
website at:

      http://www.adaptivepath.com/publications/essays/archives/000385.php


HTH,
Ian

It's better to be hated for who you are
than loved for who you are not

Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078


                                                                       
                      Yves Vindevogel                                  
                      <[EMAIL PROTECTED]        To:       
[email protected]
                      lements.be>                 cc:                  
                                                  Subject:  Re: Cocoon and 
OpenLaszlo
                      08/30/2005 11:43 AM                              
                      Please respond to                                
                      users                                            
                                                                       




Afaik, Ajax is a way to render content on the client side, a bit what
is done by the cocoon pipelines.

On 30 Aug 2005, at 16:56, Marc Salvetti wrote:

>
>
> Sebastien Arbogast a écrit :
>
>> Yes but do you think it's really possible to design your logical
>> documents to fit such different paradigms as the ones of HTML and
>> Laszlo ? The main discrepancy I see is that an HTML page must be built
>> once and for all (except if it uses AJAX to load data but it's still
>> an exception),
> I don't know what is AJAX, sorry :)
>
>> whereas with Laszlo, it's very common to have different
>> window's extract information from different sources after the
>> application has been loaded through the different RPC API's.
>>
>>
> As i see it, you don't do have to do any RPC from laslzo, because
> theses calls are done with cocoon on the MC side, you just feed the
> window with the same content as in html, but in one case the window is
> designed with html+css and in the other case through laszlo
> serializer.
> Hope that makes sense ;)
>
> Marc
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
Met vriendelijke groeten,
Bien à vous,
Kind regards,

Yves Vindevogel
Implements

(See attached file: Pasted Graphic 2.tiff)

Mail: [EMAIL PROTECTED]  - Mobile: +32 (478) 80 82 91

Kempische Steenweg 206 - 3500 Hasselt - Tel-Fax: +32 (11) 43 55 76

Web: http://www.implements.be

First they ignore you.  Then they laugh at you.  Then they fight you.
Then you win.
Mahatma Ghandi.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Attachment: Pasted Graphic 2.tiff
Description: TIFF image

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to