| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | emu: correct some file headers (nw) | 2020-06-19 | 1 | -2/+2 | |
| | | |||||
| * | srcclean (nw) | 2017-03-26 | 1 | -2/+2 | |
| | | |||||
| * | Refactored HTTP handling to be easier to extend and use (nw) | 2017-03-19 | 1 | -185/+3 | |
| | | |||||
| * | more workaround (nw) | 2017-02-27 | 1 | -2/+2 | |
| | | |||||
| * | don't assume thread is always started (nw) | 2017-02-24 | 1 | -3/+2 | |
| | | |||||
| * | srcclean (nw) | 2017-01-22 | 1 | -5/+5 | |
| | | |||||
| * | Removing unnecessary callback | 2017-01-15 | 1 | -1/+1 | |
| | | | | | | | | | | | I'm doing this in response to a compilation error on MSVC 2015. As far as I can tell, this is a bug in the compiler. My basis for asserting this is that placing the following declaration within the 'endpoint.on_open = <<lambda>>' gives the same compilation error: const std::function<void(void)> mycallback = [](void) {}; Whereas moving that logic outside of the 'endpoint.on_open = <<lambda>>' does not give an error. Normally I don't like working around buggy compilers, but in this case the callback is supposed to be optional anyways. | ||||
| * | Added websockets as well (nw) | 2017-01-04 | 1 | -2/+24 | |
| | | |||||
| * | Added initial HTTP/HTTPS webserver/websocket server support (nw) | 2017-01-04 | 1 | -0/+186 | |
