Re: Client Side or Server Side?
Date: 1996/05/13
Message-ID: <4n5vg9$e3a_at_gossamer.itmel.bhp.com.au>#1/1
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?
Our general rule of thumb is:
- if it involves database interaction (eg fetch, update, delete) then it
goes on the server side.
- if it doesnt then it goes on the client side
further, if there is any commonality element (generally, it doesnt specify block/ item names and has some possibility of reuse) then it goes in a common library.
This is the theory. In practice we are pretty lazy, and most program units remain in the form.
HIH
Lee
Lee Levy, ISSD Technical Dream Team, Del Code (34) BHP Information Technology, ACN 006 476 213 PO Box 261, Warrawong, NSW 2502, Australia PH: +61 42 75-5485 Fax: -5500 Tie: 8855- Internet : levy.lee.ls_at_bhp.com.au
Opinions expressed are mostly my own, so give me some credit. Received on Mon May 13 1996 - 00:00:00 CEST