Re: Client Side or Server Side?

From: Brian Spears <spears_at_mprgate.mpr.ca>
Date: 1996/05/14
Message-ID: <4nar0f$q6g_at_viking.mpr.ca>#1/1


levy.lee.ls_at_bhp.com.au (Lee Levy) writes:

: In article <319350E3.2E7E_at_ix.netcom.com>, Warren Nisley <wnisley_at_ix.netcom.com> says:

: >
: >To all,
: >
: >A big issue lately at our site has been whether to place stored
: >packages/procedures/functions on the client side or on the server side
: >of the application.
: >
: >We currently have a lot of code developed and stored on the server side. Some
: >of these objects could be migrated into form libraries on the client to help
: >performance and take some of the daytime load off the server, if necessary.
: >
: >We're running Oracle 7.2 on Sequent/Dynix with Forms 4.5 on the client side.
: >Most client PCs will have 16M of memory. The database contains approx 100
: >tables; the largest group of tables contain approx 15M rows.
: >
: >Nearly every module contains at least one fetch from a database table; many
: >are used to centralize updates/inserts for the application; we
: >don't have any purely "calculation" programs that I know of.
: >
: >Does anyone have guidelines/rules of thumb to follow in making this decision?
: >Any examples of purely client side code?
: >Any examples of purely server side code?
:

Hi,  

   Just a note, we are going through the process and we are leaving alot  

on the server and packaging code in stored procedures. It makes the forms

simpler and less taxing on network communications. Received on Tue May 14 1996 - 00:00:00 CEST

Original text of this message