Re: [opensource-dev] New HTTP Library & Project Viewer

[Teravus Ovares]

Good to see everyone having the HTTP spec discussion.This is the
preverbial elephant in the room for this network solution.

Regards

Teravus

On Tue, Oct 23, 2012 at 8:04 PM, Dahlia Trimble wrote:

> I believe the 2 persistent HTTP connections/server recommendation is just
> that: a maximum of 2 *persistent* connections *per server*. Torrent
> downloads are more likely 1 connection per server with many servers.
> Torrent clients also have the ability for users to specify maximum outbound
> transfer rates and trying to overcome them by opening more connections to a
> particular server will likely not be fruitful.
>
> Also, networked system designers may have control of how endpoints are
> implemented but if the public internet is used as a transfer medium then
> they have little (if any) control over what happens between those
> endpoints. ISPs can (and often do) control traffic via whatever criteria
> they deem fit. Choke points likely exist in many places and end users may
> be powerless to understand and/or resolve issues caused by over-zealous
> connection hoarding.
>
>
> On Tue, Oct 23, 2012 at 5:21 PM, Henri Beauchamp  wrote:
>
>> On Tue, 23 Oct 2012 10:28:37 -0400, Monty Brandenberg wrote:
>>
>> > Here's a chart I keep forwarding:
>> >
>> http://www.smallnetbuilder.com/lanwan/router-charts/bar/77-max-simul-conn
>> > Not officially endorsed by Linden, etc., but a useful measure of
>> > one metric that is likely to predict problems.  At the bottom of
>> > that chart you'll find members of router families that are both
>> > very common and very often a source of problems in SL.
>>
>> Very interesting chart... And quite frigthening too, seeing all the
>> so-called "routers" that can't even handle 1K connections !
>>
>> This said, such routers would also stall on torrent downloads.
>>
>> Henri.
>> ___
>> Policies and (un)subscribe information available here:
>> http://wiki.secondlife.com/wiki/OpenSource-Dev
>> Please read the policies before posting to keep unmoderated posting
>> privileges
>>
>
>
> ___
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>
___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

[opensource-dev] Review Request: Put the viewer version into marker files, and report errors only when the version matches

[Oz Linden]

---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/607/
---

Review request for Viewer.


Description
---

In all the marker files used to detect how the viewer run terminates, record 
the version.  When checking the results, report errors only if the current 
version matches the version in the file.  This prevents errors in one version 
from being reported against the subsequent version.


This addresses bug storm-1850.
http://jira.secondlife.com/browse/storm-1850


Diffs
-

  indra/newview/llappviewer.h 3d35a13561fc 
  indra/newview/llappviewer.cpp 3d35a13561fc 

Diff: http://codereview.secondlife.com/r/607/diff/


Testing
---

Several simulated crashes both of the modified and unmodified viewers, and some 
in which the marker file was modified manually to simulate different viewers. 
Launched the new viewer after different crashes (and normal exits) and 
confirmed (using logging temporarily added for that purpose) that the reported 
last exec event was correct - and is always reported as Normal if the previous 
version and the running version were not the same.


Thanks,

Oz Linden

___
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges