[Sigia-l] The IA in RIAs

[Dave]

What is an RIA ...

Bill asked if it has to be a connected client and I would say, Yes it does.

While RIAs is a moving backward, it is not actually a complete step
backward. Macromedia has a great chart showing the pgoression of
things in the app space.

Mainframe - everything centralized, I/O is the only thing the client
is used for. So there is a centralized installation base.

Client/Server - Installed application on user's desktop. Decentralized
install base + centralized install-base. Lots of logic/intelligence on
the client. Completely integratable with the user's desktop using OS
level APIs (desktop < > server flow of content/information/data is
possible). Lower server-side CPU cycles since so much logic exists on
the client. Lower bandwidth requirements.

Web-based - centralized application. No install on the user/client
side. Client is part of platform, decodes distributed GUI wichi is for
I/O only, but integrates with a total desktop experience. Web-app used
in the same application as many other tools. Data-connect reside in
system. No means for moving between the user's desktop and the
application. Low CPU cycle, but high packet bandwidth on the client.
the Server has tremendous CPU cycle load.

RIA - centralized application, but the distributed GUI has more
intelligence like a C/S application. Usually but not always runs
inside a client that is part of the user's platform (the browser). A
more sophisticated runtime engine is plugged into that platform
(Flash, Curl, XUL, etc.). Still no good means for moving between
desktop and the server application.

RIAs increase share in bandwidth between client and server both in
packets and CPU cycles.


Anyway, tha'ts the way I believe that Macromedia and I know the way
that I am using RIA. There needs to be some definition that separates
it from C/S solutions b/c I do believe we are not moving ALL the way
back to C/S.

-- dave