Opened 9 years ago

Closed 8 years ago

Last modified 6 years ago

#131 closed design (fixed)

increase connection limit

Reported by: julian.reschke@… Owned by:
Priority: urgent Milestone: 08
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:

Description

Part 1, section 7.1.4 recommends:

"Clients that use persistent connections SHOULD limit the number of simultaneous connections that they maintain to a given server. A single-user client SHOULD NOT maintain more than 2 connections with any server or proxy."

UAs increasingly allow more connections to take advantage of high bandwidths, we probably should consider increasing the recommended limit.

Attachments (1)

131.diff (2.4 KB) - added by julian.reschke@… 8 years ago.
Proposed patch for part 1.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 8 years ago by julian.reschke@…

  • Priority set to urgent

comment:2 Changed 8 years ago by julian.reschke@…

  • Priority changed from urgent to normal

comment:3 Changed 8 years ago by mnot@…

  • Priority changed from normal to urgent

Need to discuss in Stockholm to make sure that there's understanding about the tradeoffs/motiviation.

comment:4 Changed 8 years ago by mnot@…

Feeling in the room at Stockholm was that we should not have any specific numeric limit, but instead discuss the tradeoffs / problems, giving advice.

comment:5 Changed 8 years ago by mnot@…

  • Milestone changed from unassigned to 08

Changed 8 years ago by julian.reschke@…

Proposed patch for part 1.

comment:6 Changed 8 years ago by julian.reschke@…

From [715]:

Remove hard limit of two connections per server (see #131)

comment:7 Changed 8 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from new to closed

comment:8 Changed 6 years ago by mnot@…

  • Severity changed from Candidate WG Document to Active WG Document
Note: See TracTickets for help on using tickets.