From: Lucas F. <lu...@de...> - 2003-05-09 17:02:31
|
Hello, You thought you scared me away didn't you, with all your craziness and such? Well it's not that easy I'm afraid. I've spent the last day or so writing a server in .NET framework that keeps open a javascript file like you guys are doing. My friend who is hosting 10's of thousands of flash-based clients (yeah, that's a custom server all righty) says that the way to do it on Windows (he is using Linux) is with I/O completion ports. His tests scaled up to at least a few thousands users on one box. And I guess that the asynchronous methods in the System.Net.Sockets namespace use I/O completion ports under the hood. This uses the system thread pool for connection pooling. So I managed to write the server with only a couple hundred lines of code. It uses a regular IIS server for the upstream and then .NET remoting to communicate with the custom server and then back down again via the javascript request. Which brings me to a problem: the browser blocks execution on the javascript file so the page doesn't load. Is there a special response header I need to include? I can put the <script> tag after the closing <body> but I get some weird errors elsewhere on the page, and also the IE world icon keeps spinning. I noticed in the KnowNow demonstrations that this didn't happen. Were there iframes being used? I covet its coolness. -- Lucas Fletcher lu...@de... http://dealersinnotions.com |