Comments on: client/server architecture

By: 11011

11011 — Fri, 27 Jan 2012 11:19:48 +0000

client /server architecture is kind of architecture where you put your data in database engine called server. the client requst the data from it e.g pc

By: lexis1y

lexis1y — Mon, 23 Nov 2009 12:51:27 +0000

what is client server architecture

By: Troy Tate

Troy Tate — Wed, 19 Aug 2009 17:17:41 +0000

MrDenny – you raise a good point about process where the data is located. The only downside with that might be that the processing power may not be located there and that is the challenge in designing client/server and data networks. Caching is also a great performance enhancing technique as long as the cache data is fresh and relevant.

By: mrdenny

mrdenny — Tue, 18 Aug 2009 23:54:41 +0000

More important (IMHO) that doing all the processing at the server, is to do all the processing where ever the data is. If the users enters a bunch of stuff, and the server only needs the resulting bit value, do the processing on the client side, and send the final bit to the server. If the server contains the bulk of the data, then do the work there sending just the small set of final results to the client.

Cache as much data as possible on the client side. If they will be downloading the same looking tables thousands of times a time, either cache that within the browser somewhere, checking to see if there are new values on the server as needed or setup a lookup database on the local site where the app can get the values from.

By: technochic

technochic — Tue, 18 Aug 2009 13:34:15 +0000

Can you provide more details about what exactly you are looking for? Are there specific limitations you are concerned about, and if so, what specifically? Thanks!