Vadim,
Smaller round trips in my case are more important. The XML coming in the
final Post is quite large. I think as a best practice when a form goes
more than a page and a half and requires thorough validation on the client
javascript starts to become less desirable. For us, catching the errors on
the front app server effectively is more important. In fact it can be
optimized specifically to handle this and Cocoon, while the back-end app
server does Product specific processing and deals with the database. The
back-end can also be optimized for transforming and handling distributed
transactions that hits two or more financial products.
-Adam
"Vadim Gritsenko"
<vadim.gritsenko@v To:
<[EMAIL PROTECTED]>
erizon.net> cc:
Subject: RE: Logging and Form
Validation
06/07/02 03:24 PM
Please respond to
cocoon-users
> From: Hunsberger, Peter [mailto:[EMAIL PROTECTED]]
>
> > (remember, you still must have validation on the backend)
>
> Precisely my original point: since you have to write the server side
> validation anyway, do you really want to write both client and server
side
> validation?
It is standard to have client-side validation in my current client
company. And it makes sense most of the time - you want to keep count of
round trips low.
Otherwise, what web developers would do? ;)
Vadim
> I only do so if there is a real performance penalty with the
> page validation/regeneration on the server side...
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
