AJAX interaction is always good for traction these days, just as a cool UI has always been attractive. The speration of presentation and application implementation is great and obviously nothing new or particular to SCA. Is fine grained service interaction with the UI a good thing from a performance perspective ?
Reworking the Big Bank sample s.t it is cleanly broken up into service components, and providing a good tutorial for replacing service components with other provided implementations is where this should go. Another good tutorial that could go with the samples would be taking the service components of big bank and creating a new completely different application from scratch reusing the service components. This tutorial could/should discuss developing generalized non application specific services where possible which is where the potential benefits from SCA reside. I will think on this some more next week but would be really interested in more thoughts on this topic and would probably enjoy working on it. Enjoy, Robbie On 8/9/06, Jeremy Boynes <[EMAIL PROTECTED]> wrote:
On Aug 9, 2006, at 12:29 PM, Luciano Resende wrote: > Hi Jeremy > > I'd be interested in working on some variation of BigBank or > maybe a new > sample scenarion that would use a Ajax front end. Do you have any > toughts on > possible scenarios, or areas you would like to exercise in this ajax > sample....otherwise I could think of something... I have this belief that SCA would make a good platform for building the server-side handlers for Ajax components. In that mode, the presentation side is done in the browser and the UI widgets make calls to the server consuming services just like anything else. This is a fine-grained, close-coupled service architecture between the browser and the host server. A simple scenario to demonstrate this would be to supplement a traditional JSP UI with one based on Ajax. For example, suppose we have an application with a set of services that provide its business logic that get called from server-based UI code (JSP, Struts, Spring, something) - this would be the traditional (dumb-browser) model. We then supplement that with an Ajax front-end which replaces the UI code with client-side JavaScript but leaves *all* the business logic unchanged. This shows how easy it is to implement this class of application on top of a service-based architecture. One way would be to take an application like MyValue, separate the UI from the services and then add the JS client code. -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- * * * Charlie * * * Check out some pics of little Charlie at http://www.flickr.com/photos/[EMAIL PROTECTED]/sets/ * * * Addresss * * * 1914 Overland Drive Chapel Hill NC 27517 * * * Number * * * 919-225-1553
