Re: Submitting as POST. Why?
| From: | Robert Cummings | Date: | Sat, 07 Apr 2007 13:01:02 +0000 |
| Subject: | Re: Submitting as POST. Why? | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-252193@lists.php.net to get a copy of this message | ||
On Sat, 2007-04-07 at 13:59 +0100, Stut wrote:
> Robert Cummings wrote:
> > On Sat, 2007-04-07 at 11:10 +0100, Stut wrote:
> >> These implied "rules" have existed since HTTP was invented, and when you
> >> think about it they make a lot of sense. They also get emphasized by the
> >> existance of so-called web accelerators that simply pre-fetch URLs on
> >> the page the user is viewing. If you have simple links (i.e. get
> >> requests) that make changes to your websites data or state, the
> >> accelerator will seriously screw it up.
> >
> > "Accelerator" *lol*. This is a terrible waste of bandwidth. So the
> > "accelerator" downloads 50 pages linking from the first page you hit and
> > after spending 5 minutes reading the first page you decide not to visit
> > any of the other links. Fast for the user maybe, but if everyone used
> > this, it would be slower overall since the net would be plugged with 90%
> > pointless requests.
>
> Indeed, I never said they were a good thing, just that we need to be
> aware that they exist and how they work.
Yep, wasn't pointing any fingies at you, was just a comment following
your post for the greater audience :)
Cheers,
Rob.
--
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com
|
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting |
| a powerful, scalable system for accessing system services |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for |
| creating re-usable components quickly and easily. |
`------------------------------------------------------------'