PROPOSED REMOTING FUNCTIONALITY - GOALS:
The remoting support in Shale should be focused on providing
client-technology-agnostic mapping of incoming HTTP requests to server side
dynamic logic for AJAX-enabled widgets (including AJAX-enabled JavaServer
Faces components), plus an easy way to serve static resources (from either
the web application itself or from class loader resources) that the client
side widgets might require. This support must operate in either a servlet
or portlet environment, and require minimal (ideally none in the simplest
case) configuration at the application level.
Great, but there are other remoting types, like AMF, Soap, etc. Could
other protocols be pluged in to request and return from chain?
And other "ui" of course other than (short lived I predict)
JavaScript/DHTML.
JDNC, Flash components (flash 8.5 has a cool new VM)
If I plug in the ADF sf.net, could I process flash requests? I don't
need you to implement it, as long as there is a "plugin" mechanism,
especially for binary protocols.
PROPOSED REMOTING FUNCTIONALITY - IMPLEMENTATION STRATEGY:
* (Optional) alternative dynamic execution mapping to execute a Commons
Chain command
(essentially equivalent to the current functionality, and/or a tie-in to
Struts Action Framework 1.3.x
type processing logic).
* (Optional) alternative dynamic execution mapping to execute an XWork
action (essentially
equivalent to what WebWork currently does for mapping incoming URLs to
business logic).
Great that WebWork and "Clasic" are in there or could be pluged in.
Ideally Shale is JSF centric but allowed other view types (and remoting
protocols)
.V
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
