Vinnie Falco 86342dd72b Use executor_work_guard in composed operations: ...

fix #1076

As per Asio and Networking TS requirements, composed operations must
maintain an object of type executor_work_guard for the executor associated
with the I/O object, for the lifetime of the asynchronous operation.

This is in addition to the requirement for maintaining an object of type
executor_work_guard for the executor associated with the handler.

2018-04-10 08:03:04 -07:00

..

basic_parser.ipp

Remove BOOST_VERSION checks

2018-01-12 12:30:39 -08:00

chunk_encode.ipp

Fields::writer replaces Fields::reader (API Change):

2017-10-30 17:53:59 -07:00

error.ipp

Tidy up namespace qualifiers

2017-07-28 17:07:23 -07:00

field.ipp

Add Access-Control-Expose-Headers field constant:

2018-03-09 09:29:14 -08:00

fields.ipp

Some basic_fields operations now give the strong exception guarantee

2018-02-26 17:09:47 -08:00

file_body_win32.ipp

Use executor_work_guard in composed operations:

2018-04-10 08:03:04 -07:00

message.ipp

Fix prepare_payload: chunked is HTTP/1.1

2017-10-27 11:16:10 -07:00

parser.ipp

New BodyReader and BodyWriter constructors (API Change):

2017-12-15 09:27:39 -08:00

read.ipp

Use executor_work_guard in composed operations:

2018-04-10 08:03:04 -07:00

rfc7230.ipp

Update copyrights

2017-07-24 09:42:51 -07:00

serializer.ipp

Fix fallthrough warnings

2018-02-16 10:51:28 -08:00

status.ipp

Remove BOOST_VERSION checks

2018-01-12 12:30:39 -08:00

verb.ipp

Tidy up a warning

2018-03-11 14:22:50 -07:00

write.ipp

Use executor_work_guard in composed operations:

2018-04-10 08:03:04 -07:00