| Some quick questions: 1) How many users will it have? And are these users all internal to the company (i.e. onsite and you can dictate their hardware/software decisions)? 2) What do you mean by thin client? I usually use thin client to mean a software client/server architecture, such as web app/web server, where most the smarts/work is done on the server. But I think you mean something different - does your "thin client" imply some type of hardware (i.e. are you referring to a blade client and heavy server hardware setup)? 3) If the answer to #2 is hardware, then my next question would be what type of client/server architecture do you need/want? A thick client (which does most the work) talking directly to the DB (or to a thin server which wraps the DB)? You seem set against HTML web app, but there are other options there as well (Flash, Java web start, etc.). Walter. On Oct 14, 2005, at 9:44 AM, Matthew Jarvis wrote:
|
_______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
