Very good info.

The spec gods also state:

GET is for reliable repeatable tasks
POST is for one time, in some order type tasks.

So the examples given fit well there.

Thor HW
Any misquote of the spec gods is entirely mine.
------------------------
From: "Wilson. P" <[EMAIL PROTECTED]>
Subject:      Re: Basic doubt
To: [EMAIL PROTECTED]
Status: R

This is a multi-part message in MIME format.
--------------80203ACB4F374E15DA9B24C0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi

If u use dopost, the parameters as well as their values won't appear in the
URL. So, If u r doing any insert update , delete transactions  then u can go
for this.

On the otherhand,if u use doGet,the parameters and their values would appear in
the URL. So, u can use in for retrieve , select statements. One more advantage
here is, users who access the page can bookmark that page and can  directly
visit that page.


Hope our folks can add more .....to get clarified.


regards
wilson

"Srinivasan S (Systems Engineering Group)" wrote:

> Hello people,
>
>         I have a basic doubt in servlets what is the difference
>         between an service method and doPost and doGet methods
>         could u please explain me in detail abt this with an
>         example please i referred lot of examples but none
>         was forthcoming please help me to understand.
>
>         I have a windowNT4.0 workstation how do i make as a
>         servlet server so that people access them.  If this is
>         not  possible in NT leme know how to do it in a solaris
>         machine so that i can configure my solaris server
>
> Thanks
> Srini

___________________________________________________________________________
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

Reply via email to