Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 70415 invoked from network); 1 Jun 2000 14:04:19 -0000 Received: from njmail.woodbridge.agency.com (199.105.243.4) by locus.apache.org with SMTP; 1 Jun 2000 14:04:19 -0000 Received: by njmail.woodbridge.agency.com with Internet Mail Service (5.5.2448.0) id ; Thu, 1 Jun 2000 10:01:38 -0400 Message-ID: From: Jason Reid To: "'cocoon-dev@xml.apache.org'" Subject: RE: Cocoon2 Design Date: Thu, 1 Jun 2000 10:01:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > Let's make a possible example: > > 1) you request "GET /employee/add" from your HTML browser > 2) Cocoon returns you an HTML form with the proper pre-commit > validation > logic (implemented as ECMAScript, for example) > 3) you submit "POST /employee/add" from the above form > 4) Cocoon returns you with the response from the above action (which > might redirect you to another resource). Step 4 has been the one that I have wrestled with for a long time... what is the cleanest mechanism for a web "application" to know where to send you next? > Jason Reid Technical Consultant AGENCY.COM 100 Woodbridge Center Drive, Suite 102 Woodbridge, NJ 07095 Email: jreid@agency.com http://www.agency.com "Do not meddle in the affairs of programmers, for they are subtle and quick to anger."