DataReductionProxy should have a session object |
||||
Issue descriptionDataReductionProxy acts within a session that has an associated ID. Because of various constraints the session's lifetime is managed by DataReductionProxy itself, but it's lifetime should be made explicit in a seperate object that holds session ID and controls Page IDs.
,
Nov 8 2017
,
Dec 27 2017
Refreshed during triage. ryansturm: Can we define what a session is? I can think of different definitions: Is it one single continuous network connection? Period during which the same proxy auth key is used? Continuous period during which the app is running in the foreground or background?
,
Dec 27 2017
Essentially we have a few objects such as headers, config, etc. that should all be under 1 master object. This object would essentially contains all the information related to the client config request. This is a request for a refactor, but can be closed if it is not worth it.
,
Feb 13 2018
Refreshed during triage.
,
Mar 27 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bengr@chromium.org
, Apr 30 2017Status: Available (was: Assigned)