missing edit-log entry for this revision
converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 30:||Line 30:|
|[http://188.8.131.52:14567/JERICHO.jpg Snapshot of this Idea]||[[http://184.108.40.206:14567/JERICHO.jpg|Snapshot of this Idea]]|
Struts 2.0 and StrutsJerichoState: an addendum to StrutsJericho
Let us consider ==> and <== and <==> to be bivalent operators such that A <==> B means that A is somehow bound to B and B is somehow bound to A.
The MVC design achitecture (not pattern) in Struts is, let us say, "webMVC", which will mean that contiguous and continguous parts of the architecture alone are bound together, or:
VIEW <==> CONTROLLER <==> MODEL <==> MODEL DATA
This "picture" considers the "VIEW" to be JSP, Velocity, etc. rather than the HTML, which is the real "VIEW".
One of the difficulties with writing web apps is that the app storage is never quite right, i.e. the scopes request, page, session, and application do not fit app needs. What is more, lacking any reasonable facade for these scopes, there is a lot of extremely repetitive hard coding relating to them that makes taglibs over complicated and workflows rather mysterious. What is needed, I suspect, is a storage unit for app state relating to the view. Something like:
VIEW <==> STATE <==> MODEL
"STATE" here are classes which are accessible from the VIEW and communicate with the MODEL. In this architecture, SCOPES, e.g. request, page, session, application, should be considered to be an element, like VIEW, CONTROLLER, MODEL, MODEL DATA and STATE. Likewise, the HTML should be considered to be "one with" (aum) the RESPONSE. So, "VIEW", remember, is the dynamic view app, such as JSP or Velocity.
Below is a snapshot of what I have in mind. I have been doing some things like this for a while.
If anyone else is interested, I will consider finding a spot we can work together on this.
I have also considered creating a JerichoFaces for the chaining. But, that is later, for now, and much more ambitious!
Involved Developers (everyone welcome -- this is a working community open to fundamental suggestions)
State Definitions Relating to Requirements
Screen = df. The interface between the user (person, machine) and the View. For example, the monitor which renders what the browser "sees".
View = df. The file or other data that is read to create this "screen". E.g. the HTML file read by the browser.
Client Viewing <==> Screen <==> Client Delivery App <==> View
View Entities = df. Files which either not the View source (HTML for a browser) but which when read "render" the View source, for example JSP, Velocity, etc. Also called "Dynamic View Entities".
View <==> Server Side State Crestion <==> View Entities
=== View Entity Renderers == View Entity Renderers = df. Code in the View Entities that renders the View and which relates either to the "look" of the View or to resources on the client or server side.
View <==> View Entity Renderers <==> View Entites
Look Renderer = df. Code which renders markup language alone in the View.
Distinguish between Model Data and View Data (State)
View Data = df. Data that is presently being accessed (streamed), being held (viewed, cached) by the View, or that is on the server side but is relating to processes and to actions which the view (end user) is presently undertaking. Model Data = df. Data store.
State Assumption = df. Something in the Screen which assumes a data state which may or may not exist at the time a request is made. (Necessary to define and to keep in the processing algorithms relating to state management. E.g. this situation should be "earmarked" and then checked on a request. If the assumed state has changed, then the screen should reject the request (if relevant to the state change) and both inform the user of the change and provide a new screen reflecting the change. This is related to but different from notifications that requests were not successfully processed.