Re: doPost versus doGet - DESIGN DECISION???

[Charles Forsythe]

> *****Approach 1****: servlet has BOTH doGet and doPost. doGet serves URL
> requests and doPost serves button presses and such events

I'd go with this approach.

If you allow people to GET pages which should get POSTed to, then people can set
bookmarks on POSTable pages.  This, at the very least, may confuse your
application.  Worse yet, it may create security issues if sensitive data ends up
stored in a bookmark URL.

-- Charles

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html