Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


Blocking a HTTP request for streaming


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
No replies to this topic

#1 Niels   Members   -  Reputation: 122

Like
Likes
Like

Posted 10 September 1999 - 07:17 AM

HTTP is a superior protocol for one particular reason: It bypasses firewalls.

It has one major drawback though, it requires a request from a client before a server can send a reply. I.e. the server cannot initiate the data transfer. For gaming purposes this means seriously inefficient polling...

I had this idea though, what if the server didn't close the return stream, but kept it open. Wouldn't that provide an open path to the client? Or would some higher level system service make it timeout?

From a performance perspective, it is not worse than keeping an open socket connection (because that's essentially what it is)!

Have anyone had any experience in this area?

/NJ


Sponsor:



Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS