Hi, I currently have a few ajax actions working in one of my applications for auto-completing drop downs and background form submission. It currently uses the _javascript_ from http://script.aculo.us/ for providing the ajax bits and I simply name forms/divs and point my asynchronous requests to a direct action that spits out some html snippets to be fed back into the page ( there is also a little css skullduggery). The only things i found that one needs to be wary of are sessions, the pushing of these background requests onto the undo stack messing up your state and also failing back to something that works in older browsers. From memory there was discussion on the list last year discussing how to handle not screwing up sessions and application state. I also, for the autocompleters, reduce the size of the result set and use raw rows so that the background action does not go and fault a whole pile of eo's on every request, which happens on each keypress. I do have a simple framework, but this is more for handling failover and display normal components and fire normal actictions than direct webobjects integration as the _javascript_ in most cases just takes an element name and a url for the asyc requst. I shall get back to css evil now. John. On 26/01/2006, at 9:15 AM, Mohapatra Ashish wrote:
|
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
