W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

state management on connections

From: Stefan Eissing <stefan.eissing@greenbytes.de>
Date: Wed, 23 Jan 2013 10:40:54 +0100
Message-Id: <896143D9-6F5A-464F-BA59-81DE5031FE3E@greenbytes.de>
To: Group HTTP Working <ietf-http-wg@w3.org>
With regards to state management on http2 connections and the burden it
imposes on servers, my understanding is:

- both endpoints of the communication built up the same "state" during
  header compression
- connection lifetime is ideally as long as clients want
- servers may run into problems regarding memory needs per connection
- clients have no problem keeping state

What if the server could somehow get rid of the state when it wants to,
without closing the connection?

Possibilities:
a) Introduce a "header reset" control frame 
b) Allow the server to retrieve the "state" from the client

Approach a) has the disadvantage of requiring communication when the
server just wants to deallocate resources.

Approach b) has the drawback that servers need to pull the state 
from the client while working on incoming requests after state clearing.
Also, certain compression schemes do require "state" to remain in sync
with requests. So retrieving state n+1 while decoding a request based
on state n might not work.

Have people really knowledgable in the server side considered
anything along these lines?

Stefan

<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Received on Wednesday, 23 January 2013 09:41:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 23 January 2013 09:41:17 GMT