On 31/07/2012 9:13 AM, Henri Beauchamp wrote:
> On Mon, 30 Jul 2012 13:08:18 -0400, Oz Linden (Scott Lawrence) wrote:
>
>> HTTP itself recommends that clients not maintain more than 2 connections
>> to the same service [1]. I don't know exactly what limit we will decide
>> is reasonable (I expe
On Mon, 30 Jul 2012 13:08:18 -0400, Oz Linden (Scott Lawrence) wrote:
> On 2012-07-29 04:07 , Henri Beauchamp wrote:
> > With just a few tweakings to the texture fetcher (and in particular
> > a setting that permits up to 32 concurrent HTTP fetches),
>
> Caution... once we begin supporting persis
On Mon, Jul 30, 2012 at 3:04 PM, Monty Brandenberg wrote:
> On 7/30/2012 5:03 PM, Tateru Nino wrote:
>>
>> Heck, I know one person with two. A
>> Belkin G *and* a Linksys WRT.
>
> There's someone who I would like to buy a drink.
Im using my old wrt54gs with dd-wrt as a wireless access point/wired
On 7/30/2012 5:03 PM, Tateru Nino wrote:
>
> Heck, I know one person with two. A
> Belkin G *and* a Linksys WRT.
There's someone who I would like to buy a drink.
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/
On 31/07/2012 3:20 AM, Oz Linden (Scott Lawrence) wrote:
> On 2012-07-29 13:58 , Sheet Spotter wrote:
>> Does increasing the HTTP connection limit also increase the burden on the
>> server and network?
>>
>> Increasing the HTTP connection limit on one client might improve the
>> experience for one
On 31/07/2012 5:28 AM, Monty Brandenberg wrote:
> On 7/30/2012 2:15 PM, Celierra Darling wrote:
>
>> FYI, the Firefox folks had a conversation in 2008 and decided to bump up
>> from 2 to 6 by default at that time (partly because everyone else was
>> raising it).[1] (And for what it's worth, I fou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/30/2012 10:20 AM, Oz Linden (Scott Lawrence) wrote:
> Opening many connections also puts additional strain on routers in
> the path that are doing connection tracking (which too many do),
> adding another possible source of problems.
It's a known
That's two connections at the process level, so that is not the limit for
each machine. For example, in hardware, each server machine may have eight
network cards on PC motherboards (by what was on the market), so each card
can have 12 connections for each server process, and each client process
h
On 7/30/2012 2:15 PM, Celierra Darling wrote:
> FYI, the Firefox folks had a conversation in 2008 and decided to bump up
> from 2 to 6 by default at that time (partly because everyone else was
> raising it).[1] (And for what it's worth, I found a mention from '06
> that "anything above 10 is exce
On Mon, Jul 30, 2012 at 1:08 PM, Oz Linden (Scott Lawrence)
wrote:
>
> On 2012-07-29 04:07 , Henri Beauchamp wrote:
>
> With just a few tweakings to the texture fetcher (and in particular
> a setting that permits up to 32 concurrent HTTP fetches),
>
>
> Caution... once we begin supporting persiste
On 2012-07-29 13:58 , Sheet Spotter wrote:
> Does increasing the HTTP connection limit also increase the burden on the
> server and network?
>
> Increasing the HTTP connection limit on one client might improve the
> experience for one person. It might also diminish the experience for
> everyone els
On 2012-07-29 04:07 , Henri Beauchamp wrote:
With just a few tweakings to the texture fetcher (and in particular
a setting that permits up to 32 concurrent HTTP fetches),
Caution... once we begin supporting persistent connections and pipelined
requests on the server side (we're working on it),
12 matches
Mail list logo
