|
|
|
Perhaps the
first fundamental common capability that the rich web application backplane
could provide is a data object. It
could expose XML serialization and addressing of data as XML based on XPath,
but it could also offer other serializations and addressing schemes.
|
|
Access to the
data can be provided by access binding so that views and controllers can
obtain and manipulate the data. Based
on bindings, mutations of data could result in direct notification events to
bound objects such as view controls.
|
|
Components may
also learn about and respond to data mutations based on events that flow
along the ancestor path between the data and the document root.
|
|
This diagram
shows controllers on the left and view components on the right, both of which
can consume data and data mutations and even produce data mutations by either
method.
|
|
Controllers can
be components like a submission object, perhaps wrapping a web service, that
changes the data based on results of the submission. Or the SCXML (state chart XML) component,
which could control application transitions based on data mutations.
|
|
Views are
objects that expose data or the ability to mutate data to the presentation
layer. Simple examples are input and
select controls as well as an output only control.
|
|
The XAC
component, or XML application component, is a recursion on the overall
architectural depiction. In other
words, all or any part of the overall diagram can appear again within an XAC. More about that in the next talk of this
session.
|
|
|
