Here is the outline of my talk from the Rev Confab. It could serve as a basis for discussion and/or choosing areas of interest for you and others who are interested.
You may also want to look at our company's site for discussion (and hype) regarding thin client and desktop web appliances:
http://www.daniels-mara.com
Best,
Jerry
**************************
DESKTOP WEB APPLIANCES (aka “Thin Clients”)
WHY THIN CLIENT?
High perceived value (e.g., iTunes, Groove)
Offers control:
Financial
Security
Presentation
Facilitates data entry (great for admin modules)
Easy to deploy (double click)
Adjunct to web apps
A marketable $ervice (a great differentiator)DEVELOPMENT
N-tier is cool:
Teamwork
Distributed logic
Scaleable back-end:
Web server & flat file
Web, app & dbase server
Scaleable services:
Formal (web services)
Informal (JML - Jerry Markup Language)
Re-use by broswers!ARCHITECTURE
N-tier:
Client
Web/App Server
Data Repository
Client variations:
Static
Dynamic
Back-end variations:
Database
Flat fileEXAMPLES
FCSA:
Static client (Rev)
Web Server (Apache)
Database (MySQL)
App server (PHP)
WZT:
Dynamic client (Rev)
Web Server (Apache)
Flat files (encrypted Stacks)
NOTE: No files stored; memory-based.On Jan 15, 2004, at 10:53 AM, Jim Lyons wrote:
Jerry Daniels wrote:
Here are 12 reasons that I like/prefer N-Tier (client-web server/app server-database) architecture: .... Hopefully, all that answers at least some of your questions. Let me know if you have more.
I am one of the many Rev users who wish they could have been at the conference, and my main interest in going was the session on using Rev "thin clients" with a PHP/MySQL server. I have done some limited development in the past with DB-backed sites, and have groaned with frustration trying to make a decent user interface in a browser. I am giddy with the possibilities of using a Rev app as my front end for private collaboration sites I am working on.
Anyway, now I want to get into the nuts and bolts of this. Are there resources available from your session, or other resources for guidance/tips/examples on implementing this? Thanks.
Jim Lyons
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
