smart vs fat

[Ginny Caughey [MVP]]

davy,

I'd say you have both. The "smart" part is the dual on-line/off-line
capability, and the "fat" part is the rich user interface that doesn't
require an internet connection.

As to your specific questions, yours could be both easy to deploy and update
because it could be small enough to download and doesn't require an
administrator to install. An example of the reverse might be a desktop app
that required a local database that had to be installed as a service and
tuned by a DBA.

The Patterns and Practices group at Microsoft has put together an Updater
Application Block that shows how to create an app that checks to see if it
needs to update itself to a newer version and then does so:
http://msdn.microsoft.com/library/d...y/en-us/dnnetcomp/html/DeploymentPatterns.asp
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/updaterv2.asp
are good starting points.

 

[davy]

About smart clients:

1) Rich user interface

2) Responsive

3) Offline capabilities

4) Easy to update

5) Easy to deploy

6) Easy to manage


I have now an application for PDA,

it registers information to the local database and synchronise these
data via web services to a remote database.

question1:
Do I have a smart client or a fat client? I would say a smart client
because it operates local and exchange information with remote systems?

thus: 1) ok
2)ok
3)ok
4)easy to update?? what makes it easier to update then fat clients
5)no experience yet, indeed easy with VS for testing purposes
6)??what do they mean


question2:
About 4) Is an example of this for example the auto-updates of windows?
Is it hard to make something like this?




question3:
This makes I can deploy software to clients. Make changes to code and
distribute these changes as updates? Yes/no && easy to get this behaviour?

question4:

about easy to deploy/manage: what are the differences in comparance with
fat clients?