|
Fawkes API
Fawkes Development Version
|
Dynamic web reply. More...
#include <>>

Public Member Functions | |
| DynamicWebReply (Code code) | |
| Constructor. More... | |
| virtual size_t | chunk_size () |
| Chunksize. More... | |
| virtual size_t | size ()=0 |
| Total size of the web reply. More... | |
| virtual size_t | next_chunk (size_t pos, char *buffer, size_t buf_max_size)=0 |
| Get data of next chunk. More... | |
Public Member Functions inherited from fawkes::WebReply | |
| WebReply (Code code) | |
| Constructor. More... | |
| virtual | ~WebReply () |
| Destructor. More... | |
| Code | code () const |
| Get response code. More... | |
| void | set_code (Code code) |
| Set response code. More... | |
| void | add_header (const std::string &header, const std::string &content) |
| Add a HTTP header. More... | |
| void | add_header (const std::string &header_string) |
| Add a HTTP header. More... | |
| const HeaderMap & | headers () const |
| get headers. More... | |
| void | set_caching (bool caching) |
| Enable or disable caching for this specific reply. More... | |
| void | set_request (WebRequest *request) |
| Set associated request. More... | |
| WebRequest * | get_request () const |
| Get associated request. More... | |
| void | pack_caching () |
| Called just before the reply is sent. More... | |
Dynamic web reply.
A reply of this type is send out in chunks, not all as a whole. It should be used for payloads that can get very large, like file transfers.
| fawkes::DynamicWebReply::DynamicWebReply | ( | Code | code | ) |
|
virtual |
|
pure virtual |
Get data of next chunk.
| pos | position in the stream. Note that a certain position may be called several times. |
| buffer | buffer to store data in |
| buf_max_size | maximum size in bytes of data that can be put into buffer |
Implemented in fawkes::DynamicMJPEGStreamWebReply, and fawkes::DynamicFileWebReply.
Referenced by fawkes::dynamic_reply_data_cb().
|
pure virtual |
Total size of the web reply.
Return the total size of the reply if known, or -1 if it is not known. In the latter case your next_chunk() method has to return -1 at some point to end the transfer. If possible by any means return a meaningful value, as it will improve the experience of users, especially for long transfers!
Implemented in fawkes::DynamicMJPEGStreamWebReply, and fawkes::DynamicFileWebReply.