Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


mmol_6453's Journal: Queues in future versions of HTTP? 1

Journal by mmol_6453

I'd read the recent article on a book about HTTP, and it ocurred to me that HTTP implementations could learn from P2P networks.

For example, Gnutella clients have queues where a client will connect periodically, and check its place in line. That way, a connection doesn't need to be maintained in order for a consumer to hold his place in line. This lets a popular server to transmit information in a true first-come-first-serve manner, rather than a manner where whoever retries.

This could seriously improve performance under times of heavy server load.

Of course, I'm no expert.

This discussion has been archived. No new comments can be posted.

Queues in future versions of HTTP?

Comments Filter:
  • but i think it's more likely a feasable feature of FTP than of HTTP. I think for HTTP it would just turn into a bottleneck. Too many administrators (at the demand of managers lacking in technical knowledge) would set it too small, or rely on server gear inadequate for their real needs. The current way of doing things is one of the checks and balances of the internet...the more traffic you have, the more server/bandwith you need. See the parallels between rush-hour traffic and this system?

    sorry for the

FORTUNE'S FUN FACTS TO KNOW AND TELL: A giant panda bear is really a member of the racoon family.