Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-tapestry Wiki" for change notification.
The following page has been changed by JesseKuhnert: http://wiki.apache.org/jakarta-tapestry/41RenderCycleDesign ------------------------------------------------------------------------------ - == High Level Overview of what "ajax" means to Tapestry == + == What "ajax" means to Tapestry == + There are many different scenerios and design choices for using ajax within web applications, but I think most of them can still be condensed into three basic types of communication: + * "'Asynchronous client requests'" with textual/xml return data from server. These are the most common types of requests. Ones that tacos primarily uses for almost all of its operations. At it's core it could be used for a million different things. Tacos uses this paradigm to manipulate what looks like a normal tapestry request into an xml document that is parseable and manageable on the client. + * "'Asynchronous JSON requests'" - These are requests like any other, but expect a very specific type of data returned from the server, data that is validily structured as [http://json.org] data. Such a structure describes a javascript object. + * "'Comet/Server data push'" - The term originally coined by alex from [http://dojotoolkit.org], describes the process of pushing data from the server to a client. This enables a slightly more dynamic user interface that doesn't involve having to constantly poll servers for new data, but it has the added drawback of having long lived open connections. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
