Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 99618 invoked by uid 500); 7 Jun 2002 17:14:52 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 99599 invoked from network); 7 Jun 2002 17:14:52 -0000 Subject: RE: Logging and Form Validation To: cocoon-users@xml.apache.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: Adam_Waldal@eFunds.com Date: Fri, 7 Jun 2002 12:14:55 -0500 X-MIMETrack: Serialize by Router on Callisto/eFunds(Release 5.0.10 |March 22, 2002) at 06/07/2002 12:14:56 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N So how would I accomplish this with Cocoon. Could I just create a component for doing that validation and treat it as a self contained pipe? -Adam "Hunsberger, Peter" To: "'cocoon-users@xml.apache.org'" Subject: RE: Logging and Form Validation 06/07/02 12:06 PM Please respond to cocoon-users > This is a major > sticking point for my developers that like and are comfortable with jsp > with javascript embedded. > They want to keep it at the client and I am trying to build a case for the > server through cocoon. IMNSHO, the only way you can justify client side validation is if you are running an Intranet and you have an organization that somehow restricts the users capability to modify browsers settings so that you can ensure JavaScript is enabled. Otherwise, you can receive unvalidated data... If you're running over the Internet it's fine to use client side validation in addition to server side if you want to have some extra performance benefits for those who have JavaScript enabled. However, who wants to maintain both? Even if you have an Intranet and locked down browser settings, client side validation can be a real pain to maintain over time. In particular, there is (usually) no good coupling between the validation and the rest of the server side code. The exception is if you generate your client side validation code from server side templates. That's quite possible, but I suspect that once you developers jump through the hoops of embedding JavaScript within XML ( lot's of escaping and/or CDATA) they won't object to server side validation nearly so much... --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: