Controlling threads in OW3b9

[Ken Case]

> There used to be a hidden "default" -- "OWTask-Web
> pages-maximumSimultaneousThreadsInGroup" -- that would control
> the number of simultaneous network connections used by
> OmniWeb.

That setting wasn't actually a direct control for the number of  
simultaneous network connections, though it certainly had an impact.

With the new HTTP 1.1 support, we now have a notion of HTTP sessions  
(network connections) which is completely independent of whether  
they're actually running in any thread.  Unfortunately, the tuning  
parameters for HTTP sessions are currently hardcoded (although they  
could be overwritten by a plug-in) rather than looked up in defaults:  
 we'll pipeline up to three requests in a single session (HTTP 1.1  
supports asking for more than one file at a time without waiting for  
the file to actually come back), and we'll create up to four sessions  
with a single HTTP server.  We'll make those settings tunable for  
the next release.

(In the mean time, if you're a developer, you could either write a  
plug-in to override OWHTTPSessionQueue's  
-maximumNumberOfRequestsToPipeline and +maximumSessionsPerServer  
settings, or you could make the changes to the OWF source code  
directly and build up your own copy of the framework with those  
changes.)

				Ken