Hi all ,
But my problem still posed .
Any idea about how you have wrote the "LiveLinks" servlet or whatever
"ServletXXX" provided that it was
mentionned as actionfor a Post Form in (<FORM action=ServletXXX
Method=POST>) for example.
THANKS In advance
----- Message d'origine -----
De : Chris Pratt <[EMAIL PROTECTED]>
A : <[EMAIL PROTECTED]>
Envoy� : lundi 20 septembre 1999 03:43
Objet : Re: Stil having Problem with POST FORM
> When you go to the site using a normal anchor tag, you see the list of
> remembered links. If you fill in the form and press the submit button
> (which is method=post), you submit that information. Like I said, it's
just
> an example. As for the file://name things, that's Outlook express trying
to
> help It see's the double slash and assumes it's a file url. Those are
just
> single line comments.
> (*Chris*)
>
> ----- Original Message -----
> From: sidaty <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: Servlet-interest <[EMAIL PROTECTED]>
> Sent: Saturday, September 18, 1999 6:16 AM
> Subject: Re: Re: Stil having Problem with POST FORM
>
>
> > Hi Chris ,
> > But you did not show us the body of the servlet "LiveLinks" which is i
> > suppose the action associeted to
> > the Post FORM , Since our major problem reside in that action (i mean
> > Servlet mentionned as action=....)
> >
> > And in your example there are some lines like file://name
> > what is their purpose exactly . Are they mendatory for "Livelinks" to
work
> ?
> >
> > Many thanks .
> >
> > Sidaty [EMAIL PROTECTED]
> >
> >
> >
> >
> > ----- Message d'origine -----
> > De : Chris Pratt <[EMAIL PROTECTED]>
> > A : <[EMAIL PROTECTED]>
> > Envoy� : vendredi 17 septembre 1999 18:27
> > Objet : Re: Stil having Problem with POST FORM
> >
> >
> > > Below is a simple HTML Link manager that I wrote when I was learning
> > > servlets. If a GET request comes in it displays the links it has
> > collected.
> > > If a POST request comes in, it expects to receive the information to
add
> > > another link to it's list of remembered links. Pretty simplistic, but
> > > different behavior between the get and post sides. It's not the most
> > > efficient beast, but it's a pretty good example program.
> > > (*Chris*)
> > >
>
> Source Removed
>
> > > ----- Original Message -----
> > > From: ARCHAIMBAULT SYLVAIN SOPRA
> <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Friday, September 17, 1999 1:01 AM
> > > Subject: Re: Stil having Problem with POST FORM
> > >
> > >
> > > > For my part, I make the same thing as Steven, because I really
> > > > don't see why you will want different behaviour with GET and POST
> > > > method. Can you give us an example of a situation in which you
> > > > want to do that.
> > > >
> > > > sly
> > > >
> > > > From: [EMAIL PROTECTED]
> > > > To: [EMAIL PROTECTED]
> > > > Date: Thu, 16 Sep 1999 11:43:28 -0500
> > > > Subject: Re: Still having Problem with POST FORM
> > > >
> > > > On Thu, 16 Sep 1999, Steven J. Owens wrote:
> > > >
> > > > [ ... ]
> > > > > Frankly, I override the service() method. Various people
> > > > have
> > > > > said "this is bad" but I've never actually heard a coherent,
> > > > cogent
> > > > > explanation of why it's bad. 99% of the time you don't really
> > > > care
> > > > > whether they use GET or POST. The main reason not to use GET is
> > > > for
> > > > [ ... ]
> > > >
> > > > Or perhaps you just didn't appreciate those explanations. What
> > > > the
> > > > default service() does is very nice, farming requests out to
> > > > appropriate doXXX() methods. So when you want to do different
> > > > things
> > > > with GET and POST (or whatever) HTTP methods, it's very nice. And
> > > > still it's very easy to handle the case when they do the same
> > > > thing.
> > > >
> > > > Perhaps you've only worked with servlets that do the same thing
> > > > with
> > > > GET and POST. But that doesn't mean that 99% of applications work
> > > > that way. And if you ever have to change, it'll be a lot easier
> > > > if
> > > > you had just left service() alone in the first place.
> > > >
> > > > In addition, not having heard a compelling argument for not
> > > > overriding
> > > > service() is *not* a compelling argument *for* overriding
> > > > service().
> > > >
> > > > Milt Epstein
> > > > Research Programmer
> > > > Software/Systems Development Group
> > > > Computing and Communications Services Office (CCSO)
> > > > University of Illinois at Urbana-Champaign (UIUC)
> > > > [EMAIL PROTECTED]
>
>
___________________________________________________________________________
> 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
___________________________________________________________________________
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
