ABANDONED CL: Making ResourceRequestBody part of //content's public API.

ABANDONED - restarted the CL with a clean slate in https://codereview.chromium.org/2038813003/

---------------------

Making ResourceRequestBody part of //content's public API.

This CL adds support for passing ResourceRequestBody instances outside
of //content layer.  This will be utilized by a later CL that needs to
add ResourceRequestBody to OpenURLParams (already part of //content's
public API) in order to support passing POST body from a form that
targets a remote frame (aka an OOPIF).

Outside of //content layer, ResourceRequestBody exposes only minimal
functionality:
1. Ability to create it from a vector of bytes (to support passing
   post body in case of a browser initiated post navigation).
2. Ability to ref-count.
There are no scenarios today where content of ResourceRequestBody would
need to be inspected outside of //content's internal implementation
details.

BUG=585284
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation

[Łukasz Anforowicz, 2016-05-23 18:51:52]

Description was changed from

==========
Making ResourceRequestBody part of //content's public API.

This CL adds support for passing ResourceRequestBody instances outside
of //content layer.  This will be utilized by a later CL that needs to
add ResourceRequestBody to OpenURLParams (already part of //content's
public API) in order to support passing POST body from a form that
targets a remote frame (aka an OOPIF).

Outside of //content layer, ResourceRequestBody exposes only minimal
functionality:
1. Ability to create it from a vector of bytes (to support passing
   post body in case of a browser initiated post navigation).
2. Ability to ref-count.
There are no scenarios today where content of ResourceRequestBody would
need to be inspected outside of //content's internal implementation
details.

BUG=585284
==========

to

==========
Making ResourceRequestBody part of //content's public API.

This CL adds support for passing ResourceRequestBody instances outside
of //content layer.  This will be utilized by a later CL that needs to
add ResourceRequestBody to OpenURLParams (already part of //content's
public API) in order to support passing POST body from a form that
targets a remote frame (aka an OOPIF).

Outside of //content layer, ResourceRequestBody exposes only minimal
functionality:
1. Ability to create it from a vector of bytes (to support passing
   post body in case of a browser initiated post navigation).
2. Ability to ref-count.
There are no scenarios today where content of ResourceRequestBody would
need to be inspected outside of //content's internal implementation
details.

BUG=585284
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
==========

[Łukasz Anforowicz, 2016-06-03 23:39:16]

Description was changed from

==========
Making ResourceRequestBody part of //content's public API.

This CL adds support for passing ResourceRequestBody instances outside
of //content layer.  This will be utilized by a later CL that needs to
add ResourceRequestBody to OpenURLParams (already part of //content's
public API) in order to support passing POST body from a form that
targets a remote frame (aka an OOPIF).

Outside of //content layer, ResourceRequestBody exposes only minimal
functionality:
1. Ability to create it from a vector of bytes (to support passing
   post body in case of a browser initiated post navigation).
2. Ability to ref-count.
There are no scenarios today where content of ResourceRequestBody would
need to be inspected outside of //content's internal implementation
details.

BUG=585284
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
==========

to

==========
ABANDONED - restarted the CL with a clean slate in
https://codereview.chromium.org/2038813003/

---------------------

Making ResourceRequestBody part of //content's public API.

This CL adds support for passing ResourceRequestBody instances outside
of //content layer.  This will be utilized by a later CL that needs to
add ResourceRequestBody to OpenURLParams (already part of //content's
public API) in order to support passing POST body from a form that
targets a remote frame (aka an OOPIF).

Outside of //content layer, ResourceRequestBody exposes only minimal
functionality:
1. Ability to create it from a vector of bytes (to support passing
   post body in case of a browser initiated post navigation).
2. Ability to ref-count.
There are no scenarios today where content of ResourceRequestBody would
need to be inspected outside of //content's internal implementation
details.

BUG=585284
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_site_isolation
==========