Re: frontend constraints

A copy of this was sent to kstubm03_at_my-dejanews.com (if that email address didn't require changing) On Fri, 26 Feb 1999 19:37:54 GMT, you wrote:

>Hi everybody,
> Suppose i use all the constraints at the frontend rather than
>backend in my application, then what are the advantages and
>disadvantages of doing so.
>

can't really think of any advantages to putting the constraints solely in the frontend application rather then in the server with the data... I've done it so they are in both sometimes so the client can get immediate feedback in the application that the data is no good, but i've not put it ONLY in the application.

o it'll be really really hard to add new applications later as they will have to re-implement all of these rules all over again (assuming that they are even aware of all of the rules)

o it'll be really hard to maintain these applications over time as the rules change. You'll have implemented the same constraint in 50 different places within your applications -- to change the rule, you'll have to find them all and fix them.

o every time you want to change a rule, you have to redeploy your application.

o you cut off any possible access to the data except via your application. Most people thought in the past "hey, thats ok, they'll only use my application" -- then this web thing came along and everyone wanted HTTP access to the data too, "oh no -- my application isn't involved anymore"...

>Thanks in advance.
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
 

Thomas Kyte
tkyte_at_us.oracle.com
Oracle Service Industries
Reston, VA USA

--
http://govt.us.oracle.com/    -- downloadable utilities
 
----------------------------------------------------------------------------
Opinions are mine and do not necessarily reflect those of Oracle Corporation