I have been an ardent supporter for Ajax technology. It can be very useful for websites where data loaded at a time is quite huge and we can break it up into smaller groups which can interact with Server independently and asynchronously. One of the prime example for this could be Enterprise Portals.
The other issue is how well these Frameworks are adapted for new technologies? Can they be used in Enterprise Portals where each portlet window can have same Ajax implementation frameworks and hence clashes of names, actionURL etc could be possible. Plus in portals the response is not send to the portlet at all. Can the framework adapt to such changes?
The nice part about frameworks is they "should" be able to do a lot of the glue code for you. I haven't tried any of the Ajax frameworks myself though, but I was using AJAX before AJAX was called AJAX on and off.
I took a stab at writing one, though never finished the implementation, I wrote up the design of an AJAX queue to provide an easy migration path for people to embed ajax into their applications.
The AJAX frameworks are fine to work with and to incorporate them in normal web applications. But now when it comes to Portals the things becomes a bit different. I am not sure if all these Framework can adapt to Portals. Other then that, some of portal server vendors are themselves providing some AJAX support, so one needs to be careful about choosing one framework.
But yes i do agree that a GOOD, STANDARDIZED and MATURE framework will always help in Reducing development time.
Post a Comment