June 27, 2003 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/dcorey/networkcomputingisitsimplyadifferentformofclientse.asp
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
July 10, 2003 at 12:53 am
Hi there
The differentiator, i think, is to do with connectiveness and persistence of the connectivity. In client server the connection is made and persists at all times for that client, unlike "network" computing which, but its nature, is stateless. In stateless, I am meaning that you cant persist a a bunch of screen interactions in sequence within a transaction like you can do in a client server connect. For example, I open the clientserver app, its opens a db connect (pooled), we open a form, a transaction may begin for arguement sake and 3 screens later and commit it all. In the stateless env we cant persist the transaction (easily) between such screen re-renders. The db connections come and go between calls along with calls to the business tier. As such, your locking/transaction models and design a quite different. This is a trap when porting client server apps to the web. What I see happen in the port, is applications to deliver contents via the browser, but utilise a java based or web-form type connect that "simulates" the client/server senario. The Oracle Form 6 webform type stuff is a classic example of this sort of thing going on, where by a click of a button the developer tool can create a .exe/fmx based client/server app rendered for the web or runs from the persons pc and associated exe's.
I better get back to work, just some thoughts.. there are many other issues to consider.
🙂
Cheers
Ck
Chris Kempster
Author of "SQL Server 2k for the Oracle DBA"
Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
July 10, 2003 at 6:29 am
I'm much in agreement with Chris's differentiator: state.
Web applications can have code executing on the workstation, even through the web browser. Examples are java applets, ActiveX controls, and even active scripting using VBScript or JScript, for instance. These do require an interaction between the workstation and server in these cases.
Citrix is defined as a thin-client, but except for the container, the ICA client, it doesn't require you to actively use anything on the workstation. Of course, file transfers, printer usage, and the like can blur this line again.
So you've got the case where web apps can fit the definition given for client-server computing and a thin client fitting the definition given for network computing.
Perhaps the line is so blurry that it's near impossible to separate systems into two distincts sets.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply