|
|
Posted by Jim Higson on 11/26/86 11:52
Chris Tomlinson wrote:
> "Jim Higson" <jh@333.org> wrote in message
> news:KMmdncKlNMD04izZnZ2dnUVZ8qednZ2d@eclipse.net.uk...
>
>> * Restrict number of http connections per client to image resources at
>> the server end so each person can only get one image at once, but can
>> retrieve several of any other kind of resource (HTML, CSS etc). You'd
>> just need a little script that does a few of the things the webserver
>> usually does. Not
>> sure how you would distinguish people though - doing this by IP (at least
>> until IPv6) would be bad for users behind a NAT, but maybe there is some
>> other way.
>
> Hi Jim, that's an interesting little idea, thanks. I wonder if anyone can
> expand on it.
All you do is hold back with sending the http responses until the other
image responses by the same client have completed. If you can't positively
identify the client (say, with cookies), don't hold back at all for safety
and to keep search engines happy. You'd also have to look out to make sure
you don't time out the requests.
I don't think it needs too much more explanation than that, I bet it could
be done in 50 lines of PHP (or about 4 lines of near-unreadable Perl). If
your developers don't fancy it I could write the code for you, but not for
free.
--
Jim
Navigation:
[Reply to this message]
|