8 Jul
2017
8 Jul
'17
5:50 p.m.
2017-07-01 22:38 GMT+02:00 Niall Douglas via Boost
If that's too experimental for you (though the Ranges TS is a TS just like the Networking TS), then do as Boost.Spirit does and work with iterator pairs. So for example, if I want to know what the Content-Length header is, upon query I get back an iterator pair pointing to the front of the storage and one after the end of the storage. Similarly, if I set the Content-Length header, I supply an iterator pair to the new contents.
That would be pretty bad as HTTP also involves connection management (e.g. "connection: close"). It'd work for an HTTP parser. But Beast seems pretty low-level already. -- VinÃcius dos Santos Oliveira https://vinipsmaker.github.io/