Skip to content

Commit

Permalink
Merge pull request #23 from willchan/FixUselessExtensions
Browse files Browse the repository at this point in the history 
Stop using extension <x:lt>. I don't want to run java.
  • Loading branch information
@grmocg
grmocg committed Jun 5, 2013
2 parents 10e1c18 + e05c57e commit 7fc0919
Show file tree
Hide file tree
Showing 3 changed files with 196 additions and 77 deletions.
74 changes: 73 additions & 1 deletion draft-mbelshe-spdy-00.html
View file
Expand Up @@ -1426,7 +1426,7 @@


<span class="grey">Belshe &amp; Peon Expires February 2, 2013 [Page 23]</span>
</pre><pre class='newpage'>
</pre><pre class='newpage'><a name="page-24" id="page-24" href="#page-24" class="invisible"> </a>
<span class="grey">Internet-Draft SPDY August 2012</span>


Expand All @@ -1453,6 +1453,78 @@

<span class="h5"><a name="section-2.7.4.3">2.7.4.3</a>. Defined Settings</span>

SETTINGS_UPLOAD_BANDWIDTH (1): indicates the sender's estimated
upload bandwidth for this connection. The value is an the
integral number of kilobytes per second that the sender predicts
as an expected maximum upload channel capacity.

SETTINGS_DOWNLOAD_BANDWIDTH (2): indicates the sender's estimated
download bandwidth for this connection. The value is an integral
number of kilobytes per second that the sender predicts as an
expected maximum download channel capacity.

SETTINGS_ROUND_TRIP_TIME (3): indicates the sender's estimated
round-trip-time for this connection. The round trip time is
defined as the minimum amount of time to send a control frame from
this client to the remote and receive a response. The value is
represented in milliseconds.

SETTINGS_MAX_CONCURRENT_STREAMS (4): indicates the maximum number of
concurrent streams that the sender will allow. This limit is
directional: it applies to the number of streams that the sender
permits the receiver to create. By default there is no limit. It
is recommended that this value be no smaller than 100, so as to
not unnecessarily limit parallelism.






<span class="grey">Belshe &amp; Peon Expires February 2, 2013 [Page 24]</span>
</pre><pre class='newpage'>
<span class="grey">Internet-Draft SPDY August 2012</span>


SETTINGS_CURRENT_CWND (5): indicates the sender's current TCP CWND
value.

SETTINGS_DOWNLOAD_RETRANS_RATE (6): indicates the sender's
retransmission rate (bytes retransmitted / total bytes
transmitted).

SETTINGS_INITIAL_WINDOW_SIZE (7): indicates the sender's initial
stream window size (in bytes) for new streams.

SETTINGS_CLIENT_CERTIFICATE_VECTOR_SIZE (8): indicates the sender's
(which should be the server) size of the client certificate
vector.

SETTINGS_SUPPORTING_SCHEMES (9): indicates the sender's supported
overlayering protocol schemes. The corresponding value must be a
32-bit value, and which contains flags as follows:

bit 0: http

bit 1: https

bit 2: ws

bit 3: wss

SETTINGS_FLOW_CONTROL_OPTIONS (10): indicates that streams directed
to the sender will not be subject to flow control. The least
significant bit (0x1) is set to indicate that new streams are not
flow controlled. All other bits are reserved. This setting
applies to all streams, including existing streams. These bits
cannot be cleared once set, see <a href="#section-2.7.9.4">Section 2.7.9.4</a>.

<span class="h4"><a name="section-2.7.5">2.7.5</a>. PUSH_PROMISE</span>

The PUSH_PROMISE frame (type=0x5) is used to notify the peer endpoint
in advance of streams the sender intends to initiate. The
PUSH_PROMISE frame includes the unsigned 31-bit identifier of the
stream the endpoint plans to create along with a minimal set of

</pre><br />
<span class="noprint"><small><small>Html markup produced by rfcmarkup 1.90, available from
Expand Down
72 changes: 72 additions & 0 deletions draft-mbelshe-spdy-00.txt
View file
Expand Up @@ -1312,3 +1312,75 @@ Internet-Draft SPDY August 2012

2.7.4.3. Defined Settings

SETTINGS_UPLOAD_BANDWIDTH (1): indicates the sender's estimated
upload bandwidth for this connection. The value is an the
integral number of kilobytes per second that the sender predicts
as an expected maximum upload channel capacity.

SETTINGS_DOWNLOAD_BANDWIDTH (2): indicates the sender's estimated
download bandwidth for this connection. The value is an integral
number of kilobytes per second that the sender predicts as an
expected maximum download channel capacity.

SETTINGS_ROUND_TRIP_TIME (3): indicates the sender's estimated
round-trip-time for this connection. The round trip time is
defined as the minimum amount of time to send a control frame from
this client to the remote and receive a response. The value is
represented in milliseconds.

SETTINGS_MAX_CONCURRENT_STREAMS (4): indicates the maximum number of
concurrent streams that the sender will allow. This limit is
directional: it applies to the number of streams that the sender
permits the receiver to create. By default there is no limit. It
is recommended that this value be no smaller than 100, so as to
not unnecessarily limit parallelism.






Belshe & Peon Expires February 2, 2013 [Page 24]

Internet-Draft SPDY August 2012


SETTINGS_CURRENT_CWND (5): indicates the sender's current TCP CWND
value.

SETTINGS_DOWNLOAD_RETRANS_RATE (6): indicates the sender's
retransmission rate (bytes retransmitted / total bytes
transmitted).

SETTINGS_INITIAL_WINDOW_SIZE (7): indicates the sender's initial
stream window size (in bytes) for new streams.

SETTINGS_CLIENT_CERTIFICATE_VECTOR_SIZE (8): indicates the sender's
(which should be the server) size of the client certificate
vector.

SETTINGS_SUPPORTING_SCHEMES (9): indicates the sender's supported
overlayering protocol schemes. The corresponding value must be a
32-bit value, and which contains flags as follows:

bit 0: http

bit 1: https

bit 2: ws

bit 3: wss

SETTINGS_FLOW_CONTROL_OPTIONS (10): indicates that streams directed
to the sender will not be subject to flow control. The least
significant bit (0x1) is set to indicate that new streams are not
flow controlled. All other bits are reserved. This setting
applies to all streams, including existing streams. These bits
cannot be cleared once set, see Section 2.7.9.4.

2.7.5. PUSH_PROMISE

The PUSH_PROMISE frame (type=0x5) is used to notify the peer endpoint
in advance of streams the sender intends to initiate. The
PUSH_PROMISE frame includes the unsigned 31-bit identifier of the
stream the endpoint plans to create along with a minimal set of
127 changes: 51 additions & 76 deletions draft-mbelshe-spdy-00.xml
View file
Expand Up @@ -1185,83 +1185,58 @@

<section anchor="SettingValues" title="Defined Settings">
<t>
The following settings are defined:
<list style="hanging">
<x:lt hangText="SETTINGS_UPLOAD_BANDWIDTH (1):">
<t>
indicates the sender's estimated upload bandwidth for this connection. The value
is an the integral number of kilobytes per
second that the sender predicts as an expected maximum upload channel capacity.
</t>
</x:lt>
<x:lt hangText="SETTINGS_DOWNLOAD_BANDWIDTH (2):">
<t>
indicates the sender's estimated download bandwidth for this connection. The value
is an integral number of kilobytes per
second that the sender predicts as an expected maximum download channel capacity.
</t>
</x:lt>
<x:lt hangText="SETTINGS_ROUND_TRIP_TIME (3):">
<t>
indicates the sender's estimated round-trip-time for this connection. The round
trip time is defined as the minimum amount of time to send a control frame from
this client to the remote and receive a response. The value is represented in
milliseconds.
</t>
</x:lt>
<x:lt hangText="SETTINGS_MAX_CONCURRENT_STREAMS (4):">
<t>
indicates the maximum number of concurrent streams that the sender will allow.
This limit is directional: it applies to the number
of streams that the sender permits the receiver to create. By default there is no
limit. It is recommended that this value be no smaller than 100,
so as to not unnecessarily limit parallelism.
</t>
</x:lt>
<x:lt hangText="SETTINGS_CURRENT_CWND (5):">
<t>
indicates the sender's current TCP CWND value.
</t>
</x:lt>
<x:lt hangText="SETTINGS_DOWNLOAD_RETRANS_RATE (6):">
<t>
indicates the sender's retransmission rate (bytes retransmitted / total bytes transmitted).
</t>
</x:lt>
<x:lt hangText="SETTINGS_INITIAL_WINDOW_SIZE (7):">
<t>
indicates the sender's initial stream window size (in bytes) for new streams.
</t>
</x:lt>
<x:lt hangText="SETTINGS_CLIENT_CERTIFICATE_VECTOR_SIZE (8):">
<t>
indicates the sender's (which should be the server) size of the client certificate vector.
</t>
</x:lt>
<x:lt hangText="SETTINGS_SUPPORTING_SCHEMES (9):">
<t>
indicates the sender's supported overlayering protocol schemes. The corresponding value must be a 32-bit value, and which contains flags as follows:
<list>
<t>bit 0: http</t>
<t>bit 1: https</t>
<t>bit 2: ws</t>
<t>bit 3: wss</t>
</list>
</t>
</x:lt>
<x:lt hangText="SETTINGS_FLOW_CONTROL_OPTIONS (10):">
<t>
indicates that streams directed to the sender will not
be subject to flow control. The least significant bit (0x1) is set to indicate
that new streams are not flow controlled. All other bits are reserved.
</t>
<t>
This setting applies to all streams, including existing streams.
</t>
<t>
These bits cannot be cleared once set, see <xref target="EndFlowControl"/>.
</t>
</x:lt>
<t hangText="SETTINGS_UPLOAD_BANDWIDTH (1):">
indicates the sender's estimated upload bandwidth for this connection. The value
is an the integral number of kilobytes per
second that the sender predicts as an expected maximum upload channel capacity.
</t>
<t hangText="SETTINGS_DOWNLOAD_BANDWIDTH (2):">
indicates the sender's estimated download bandwidth for this connection. The value
is an integral number of kilobytes per
second that the sender predicts as an expected maximum download channel capacity.
</t>
<t hangText="SETTINGS_ROUND_TRIP_TIME (3):">
indicates the sender's estimated round-trip-time for this connection. The round
trip time is defined as the minimum amount of time to send a control frame from
this client to the remote and receive a response. The value is represented in
milliseconds.
</t>
<t hangText="SETTINGS_MAX_CONCURRENT_STREAMS (4):">
indicates the maximum number of concurrent streams that the sender will allow.
This limit is directional: it applies to the number
of streams that the sender permits the receiver to create. By default there is no
limit. It is recommended that this value be no smaller than 100,
so as to not unnecessarily limit parallelism.
</t>
<t hangText="SETTINGS_CURRENT_CWND (5):">
indicates the sender's current TCP CWND value.
</t>
<t hangText="SETTINGS_DOWNLOAD_RETRANS_RATE (6):">
indicates the sender's retransmission rate (bytes retransmitted / total bytes transmitted).
</t>
<t hangText="SETTINGS_INITIAL_WINDOW_SIZE (7):">
indicates the sender's initial stream window size (in bytes) for new streams.
</t>
<t hangText="SETTINGS_CLIENT_CERTIFICATE_VECTOR_SIZE (8):">
indicates the sender's (which should be the server) size of the client certificate vector.
</t>
<t hangText="SETTINGS_SUPPORTING_SCHEMES (9):">
indicates the sender's supported overlayering protocol schemes. The corresponding value must be a 32-bit value, and which contains flags as follows:
<list>
<t>bit 0: http</t>
<t>bit 1: https</t>
<t>bit 2: ws</t>
<t>bit 3: wss</t>
</list>
</t>
<t hangText="SETTINGS_FLOW_CONTROL_OPTIONS (10):">
indicates that streams directed to the sender will not
be subject to flow control. The least significant bit (0x1) is set to indicate
that new streams are not flow controlled. All other bits are reserved.
This setting applies to all streams, including existing streams.
These bits cannot be cleared once set, see <xref target="EndFlowControl"/>.
</t>
</list>
</t>
</section>
Expand Down

0 comments on commit 7fc0919

Please sign in to comment.