I believe that even though client side validation is easier to code and less
load on the server, server side is still the way to go. The biggest reason
I like to stick to server side validation is the fact of the interface
design. The JS pop up windows are not only a pain in the butt for users,
but they are unattractive and look unprofessional. A good point was made
that your form should always distinguish between which fields are mandatory
and which ones aren't and as well the common code for Wireless purposes
(might not be WML since there is all that turmoil over it.... but that's a
whole other conversation). By putting the validation on the server side,
you can better customize the error message to include all of the form's
errors and not give them an ugly JS popup window...
Just my 2 cents....
Sean
-----Original Message-----
From: McCollough, Alan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 17, 2000 4:54 PM
To: '[EMAIL PROTECTED]'
Subject: RE: To CFFORM or not to CFFORM
I try to use the client-side JS as much as possible. All the less code to
write...
Alan McCollough
Web Programmer
Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Bryan [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, August 17, 2000 8:46 AM
> To: [EMAIL PROTECTED]
> Subject: To CFFORM or not to CFFORM
>
> Hey All,
>
> I've debated this issue with my local associates many times, so I
> thought I'd throw it out there and see what some other folks have to say
> about it.
>
> Do you use CFFORM and it's built in client side form element validation,
> or do you use a server side approach (i.e. do some error
> checking...build an error message and display it)?
>
> My pet peeve with CFFORM is the javascript pop-up windows show one at a
> time which could drive a user crazy. If you use a combo of both client
> and server side validation, you could confuse the user (which we all
> know get confused very quick). They think they've filled in the form
> properly and then all of a sudden they are looking at a list of new
> errors.
>
> Of course CF 4.5.1 has the "onvalidate" attribute in cfinput which
> allows you to expand the kind of validation you can do, but you're still
> stuck with one error message at a time.
>
> There is also the issue of hits on the server. Of course client side is
> better here.
>
> Comment away...suggestions welcome...custom solutions??
>
> Thanks in advance
>
> Bryan Stevenson
> Electric Canvas Technologies
> Inter/Intranet Development
> www.ecanvas.com
> [EMAIL PROTECTED]
> (250) 920-8830
> -------------------------------------------
> Allaire Alliance Partner
> www.allaire.com
>
>
> --------------------------------------------------------------------------
> ----
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
