Well the article kind of says that only domain model/dao is on the server.
And MVC is on the client. And that makes sense. So in your example, if
the client requests the XML, then it's RiA. Your's might not be a good
example.
Ajax is a perfect example. Idea was that Ti would do Ajax(clientside)
and Faces(serverside), and now I think that one framework can't do both,
as this article articulates.
.V
Michael Jouravlev wrote:
On 8/29/05, netsql <[EMAIL PROTECTED]> wrote:
As per http://osteele.com/archives/2004/08/web-mvc
I now think if a frameworks is client side rendering (Ajax, JDNC, ...)
it can't be mixed w/ a server side rednering framework, you can be
strong in one or the other (and then rig it for the other).
Clarify "rendering". What about delivering XML to the client, and
processing it on a client with XSLT? Is this client-side or
server-side rendering? The script is loaded from server anyway.
Michael.
--
thx,
.V
Broadband interface (RIA) + mail box safety = Roomity.com
<http://roomity.com/demo.jsp>
*Your* clubs, no sign up to read, ad supported; try broadband internet.
cell: 917 825 3035 in DFW
email: netsql at roomity.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
