X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id DB944D1BAE0 for ; Thu, 6 Nov 2003 19:22:53 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 39427-02 for ; Thu, 6 Nov 2003 15:22:23 -0400 (AST) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id 6C352D1BACF for ; Thu, 6 Nov 2003 15:22:21 -0400 (AST) Received: (qmail 22012 invoked by uid 500); 6 Nov 2003 19:20:38 -0000 Date: Thu, 6 Nov 2003 13:20:38 -0600 From: Bruno Wolff III To: Michael Glaesemann Cc: pgsql-php@postgresql.org Subject: Re: Reducing duplicated business rules Message-ID: <20031106192038.GA21921@wolff.to> Mail-Followup-To: Michael Glaesemann , pgsql-php@postgresql.org References: <000601c3a407$ce9a4950$0300a8c0@homer3> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/17 X-Sequence-Number: 2410 On Fri, Nov 07, 2003 at 01:16:54 +0900, Michael Glaesemann wrote: > > what you've written, I'm guessing this is exactly it. Using JavaScript > allows the client—rather than the server—do the checking. It seems to > me you'd pay an initial hit (downloading more into the client), but you > don't have to keep using the server to process/validate/check the data. > Am I close? The server still has to do the validity checking. Often pages set up this way don't work when javascript isn't available. What you save are round trips when the data is messed up. That may or may not be better depending on how large the form is wtih and without javascript, what the rate of mistakes is, what the available bandwidth is and how loaded the server is.