Last updated at 4:42 pm UTC on 31 July 2009
Web applications have a Client/Server architecture. In Seaside you can code applications as in the traditional style of web programming, using message referencing tags and scripts, but the concept of tags and document-files with scripts, etc. is not in the object technology tradition. Actually, object technology encourages to recognize the real objects you're trying to represent and use.
In the current, typical, web application scene, and this is independent of any web framework, we can find two forms of synchronization most widely used: AJAX (alternatives exists, but not so widely used) and Forms (Submit). Using one or another depends of your particular needs, although there is a moving trend to introduce AJAX functionality in web interfaces. Programming with AJAX is super easy when you have the possibility of define really simple interfaces, but it becomes harder when you have complex UI requirements, especially related with interactions, so carefully choosing which options fits more for your needs is not a bad idea at all. In the particular case of complex UI applications, consulting an experienced interaction designer is another interesting possibility.
SmallFaces (SF) provides event support for both variants of synchronization:
- As #triggerFormElement: does not work fine in Scriptaculos on the multi-select lists (see commentary of the method SUAjax>> triggerFormElement:), SFMultipleListBox does not work for the handlers of events that use Ajax. Only works fine the Submit event handler (SFDelayedEventHandler). See WAMiltipleListBoxExample
- The event handler in which we have implemented the SASE protocol uses the SUEvaluator objects, but when an error occurs it's not shown because Scriptaculoius object doesn't. See mail