On Wednesday, Jan 8, 2003, at 12:09 US/Pacific, Susan Aurand wrote:
thanks.
the simplest rule of thumb is
start with GET until you have a good excuse for POST
When you shift towards the 'all POST' approach, then you
also want to be effectively using JavaScripting for the
stuff that needs to
On Wed, 8 Jan 2003 10:02:20 -0800, drieux <[EMAIL PROTECTED]> wrote:
>
> On Wednesday, Jan 8, 2003, at 01:21 US/Pacific, Gary Stainburn wrote:
> [..]
> > The only benefits of using GET that I can think of is that you can
> > emulate a
> > form by
On Wednesday, Jan 8, 2003, at 01:21 US/Pacific, Gary Stainburn wrote:
[..]
The only benefits of using GET that I can think of is that you can
emulate a
form by manually keying the data in the URL, and you can even create a
bookmark containing the completed form details. I personally use this
t
On Tuesday 07 January 2003 9:17 pm, Susan Aurand wrote:
> I know the POST Method the data is sent to STDIN, and GET method the data
> is attached to the URL and then submitted. When and why would you want to
> use the GET method versus the POST method. Is is because of firewalls? or
> what? I wou
Susan Aurand wrote:
> I know the POST Method the data is sent to STDIN, and GET
> method the data is attached to the URL and
> then submitted. When and why would you want to use the GET
> method versus the POST method. Is is
> because of firewalls? or what? I would appreciate any input on this
>
There are many reasons to choose one or the other. A good one for POST is file
uploads, where the input values could be very very large (think mega or giga bytes of
data) or binary which would have to be encoded and then unencoded in some manner,
whereas this is less of a problem over a stream.
