Clean up FLAG_ASYNC support in //base |
||||||
Issue descriptionThis is currently layered a bit oddly: while the flag itself is defined in //base, //base itself has minimal support for async files: the only async file reader that I know of is in //net. We should try to restructure the net code to not require //base changes: in particular, maybe FileStreamContext should open the file itself with the appropriate flags and then pass the PlatformFile to File.
,
Jun 19 2018
I think we need more concrete action items here - otherwise, this bug is likely to site for 5 years before being closed as not actionable.
,
Jun 19 2018
Originally I was thinking that FLAG_ASYNC could be wholly removed from //base, since this is really only used as support for net::FileStreamContext. But it looks like we received an additional dependency from //device. Let me follow up with the owner of the //device code and figure out some concrete steps.
,
Jun 19 2018
,
Jun 27 2018
,
Jul 9
dcheng: Ping :)
,
Jul 9
[dcheng]: Marking this as assigned. Feel free to unassign once we have a path forward.
,
Jul 9
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mmenke@chromium.org
, Jun 19 2018