Deployed 8a34478 with MkDocs version: 1.0.4
This commit is contained in:
Benjamin Sergeant committed
1 parent
43d368f9a0
commit
5f05bbebac
5 files changed
+43
-9
No files matched your search
@@ -94,6 +94,17 @@
|
||||
<div class="col-md-3"><div class="bs-sidebar hidden-print affix well" role="complementary">
|
||||
<ul class="nav bs-sidenav">
|
||||
<li class="main active"><a href="#changelog">Changelog</a></li>
|
||||
<li><a href="#794-2020-01-12">[7.9.4] - 2020-01-12</a></li>
|
||||
<li><a href="#793-2020-01-10">[7.9.3] - 2020-01-10</a></li>
|
||||
<li><a href="#792-2020-01-06">[7.9.2] - 2020-01-06</a></li>
|
||||
<li><a href="#791-2020-01-06">[7.9.1] - 2020-01-06</a></li>
|
||||
<li><a href="#790-2020-01-04">[7.9.0] - 2020-01-04</a></li>
|
||||
<li><a href="#789-2020-01-04">[7.8.9] - 2020-01-04</a></li>
|
||||
<li><a href="#788-2019-12-28">[7.8.8] - 2019-12-28</a></li>
|
||||
<li><a href="#786-2019-12-28">[7.8.6] - 2019-12-28</a></li>
|
||||
<li><a href="#785-2019-12-28">[7.8.5] - 2019-12-28</a></li>
|
||||
<li><a href="#784-2019-12-27">[7.8.4] - 2019-12-27</a></li>
|
||||
<li><a href="#783-2019-12-27">[7.8.3] - 2019-12-27</a></li>
|
||||
<li><a href="#782-2019-12-25">[7.8.2] - 2019-12-25</a></li>
|
||||
<li><a href="#781-2019-12-25">[7.8.1] - 2019-12-25</a></li>
|
||||
<li><a href="#780-2019-12-24">[7.8.0] - 2019-12-24</a></li>
|
||||
@@ -174,6 +185,29 @@
|
||||
|
||||
<h1 id="changelog">Changelog</h1>
|
||||
<p>All changes to this project will be documented in this file.</p>
|
||||
<h2 id="794-2020-01-12">[7.9.4] - 2020-01-12</h2>
|
||||
<p>(openssl + mbedssl) fix #140, can send large files with ws send over ssl / still broken with apple ssl</p>
|
||||
<h2 id="793-2020-01-10">[7.9.3] - 2020-01-10</h2>
|
||||
<p>(apple ssl) model write method after the OpenSSL one for consistency</p>
|
||||
<h2 id="792-2020-01-06">[7.9.2] - 2020-01-06</h2>
|
||||
<p>(apple ssl) unify read and write ssl utility code</p>
|
||||
<h2 id="791-2020-01-06">[7.9.1] - 2020-01-06</h2>
|
||||
<p>(websocket client) better error propagation when errors are detected while sending data
|
||||
(ws send) detect failures to send big files, terminate in those cases and report error</p>
|
||||
<h2 id="790-2020-01-04">[7.9.0] - 2020-01-04</h2>
|
||||
<p>(ws send) add option (-x) to disable per message deflate compression</p>
|
||||
<h2 id="789-2020-01-04">[7.8.9] - 2020-01-04</h2>
|
||||
<p>(ws send + receive) handle all message types (ping + pong + fragment) / investigate #140</p>
|
||||
<h2 id="788-2019-12-28">[7.8.8] - 2019-12-28</h2>
|
||||
<p>(mbedtls) fix related to private key file parsing and initialization</p>
|
||||
<h2 id="786-2019-12-28">[7.8.6] - 2019-12-28</h2>
|
||||
<p>(ws cobra to sentry/statsd) fix for handling null events properly for empty queues + use queue to send data to statsd</p>
|
||||
<h2 id="785-2019-12-28">[7.8.5] - 2019-12-28</h2>
|
||||
<p>(ws cobra to sentry) handle null events for empty queues</p>
|
||||
<h2 id="784-2019-12-27">[7.8.4] - 2019-12-27</h2>
|
||||
<p>(ws cobra to sentry) game is picked in a fair manner, so that all games get the same share of sent events</p>
|
||||
<h2 id="783-2019-12-27">[7.8.3] - 2019-12-27</h2>
|
||||
<p>(ws cobra to sentry) refactor queue related code into a class</p>
|
||||
<h2 id="782-2019-12-25">[7.8.2] - 2019-12-25</h2>
|
||||
<p>(ws cobra to sentry) bound the queue size used to hold up cobra messages before they are sent to sentry. Default queue size is a 100 messages. Without such limit the program runs out of memory when a subscriber receive a lot of messages that cannot make it to sentry</p>
|
||||
<h2 id="781-2019-12-25">[7.8.1] - 2019-12-25</h2>
|
||||
|
||||
+1
-1
@@ -226,5 +226,5 @@ webSocket.send("hello world");
|
||||
|
||||
<!--
|
||||
MkDocs version : 1.0.4
|
||||
Build Date UTC : 2019-12-26 06:20:36
|
||||
Build Date UTC : 2020-01-13 19:50:06
|
||||
-->
|
||||
@@ -1 +1 @@
|
||||
{"config":{"lang":["en"],"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Introduction WebSocket is a computer communications protocol, providing full-duplex and bi-directionnal communication channels over a single TCP connection. IXWebSocket is a C++ library for client and server Websocket communication, and for client and server HTTP communication. TLS aka SSL is supported. The code is derived from easywsclient and from the Satori C SDK . It has been tested on the following platforms. macOS iOS Linux Android Windows FreeBSD Example code // Required on Windows ix::initNetSystem(); // Our websocket object ix::WebSocket webSocket; std::string url(\"ws://localhost:8080/\"); webSocket.setUrl(url); // Setup a callback to be fired when a message or an event (open, close, error) is received webSocket.setOnMessageCallback([](const ix::WebSocketMessagePtr& msg) { if (msg->type == ix::WebSocketMessageType::Message) { std::cout << msg->str << std::endl; } } ); // Now that our callback is setup, we can start our background thread and receive messages webSocket.start(); // Send a message to the server (default to TEXT mode) webSocket.send(\"hello world\"); Why another library? There are 2 main reasons that explain why IXWebSocket got written. First, we needed a C++ cross-platform client library, which should have few dependencies. What looked like the most solid one, websocketpp did depend on boost and this was not an option for us. Secondly, there were other available libraries with fewer dependencies (C ones), but they required calling an explicit poll routine periodically to know if a client had received data from a server, which was not elegant. We started by solving those 2 problems, then we added server websocket code, then an HTTP client, and finally a very simple HTTP server. Contributing IXWebSocket is developed on GitHub . We'd love to hear about how you use it; opening up an issue on GitHub is ok for that. If things don't work as expected, please create an issue on GitHub, or even better a pull request if you know how to fix your problem.","title":"Home"},{"location":"#introduction","text":"WebSocket is a computer communications protocol, providing full-duplex and bi-directionnal communication channels over a single TCP connection. IXWebSocket is a C++ library for client and server Websocket communication, and for client and server HTTP communication. TLS aka SSL is supported. The code is derived from easywsclient and from the Satori C SDK . It has been tested on the following platforms. macOS iOS Linux Android Windows FreeBSD","title":"Introduction"},{"location":"#example-code","text":"// Required on Windows ix::initNetSystem(); // Our websocket object ix::WebSocket webSocket; std::string url(\"ws://localhost:8080/\"); webSocket.setUrl(url); // Setup a callback to be fired when a message or an event (open, close, error) is received webSocket.setOnMessageCallback([](const ix::WebSocketMessagePtr& msg) { if (msg->type == ix::WebSocketMessageType::Message) { std::cout << msg->str << std::endl; } } ); // Now that our callback is setup, we can start our background thread and receive messages webSocket.start(); // Send a message to the server (default to TEXT mode) webSocket.send(\"hello world\");","title":"Example code"},{"location":"#why-another-library","text":"There are 2 main reasons that explain why IXWebSocket got written. First, we needed a C++ cross-platform client library, which should have few dependencies. What looked like the most solid one, websocketpp did depend on boost and this was not an option for us. Secondly, there were other available libraries with fewer dependencies (C ones), but they required calling an explicit poll routine periodically to know if a client had received data from a server, which was not elegant. We started by solving those 2 problems, then we added server websocket code, then an HTTP client, and finally a very simple HTTP server.","title":"Why another library?"},{"location":"#contributing","text":"IXWebSocket is developed on GitHub . We'd love to hear about how you use it; opening up an issue on GitHub is ok for that. If things don't work as expected, please create an issue on GitHub, or even better a pull request if you know how to fix your problem.","title":"Contributing"},{"location":"CHANGELOG/","text":"Changelog All changes to this project will be documented in this file. [7.8.2] - 2019-12-25 (ws cobra to sentry) bound the queue size used to hold up cobra messages before they are sent to sentry. Default queue size is a 100 messages. Without such limit the program runs out of memory when a subscriber receive a lot of messages that cannot make it to sentry [7.8.1] - 2019-12-25 (ws client) use correct compilation defines so that spdlog is not used as a header only library (reduce binary size and increase compilation speed) [7.8.0] - 2019-12-24 (ws client) all commands use spdlog instead of std::cerr or std::cout for logging [7.6.5] - 2019-Line truncated
|
||||
{"config":{"lang":["en"],"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Introduction WebSocket is a computer communications protocol, providing full-duplex and bi-directionnal communication channels over a single TCP connection. IXWebSocket is a C++ library for client and server Websocket communication, and for client and server HTTP communication. TLS aka SSL is supported. The code is derived from easywsclient and from the Satori C SDK . It has been tested on the following platforms. macOS iOS Linux Android Windows FreeBSD Example code // Required on Windows ix::initNetSystem(); // Our websocket object ix::WebSocket webSocket; std::string url(\"ws://localhost:8080/\"); webSocket.setUrl(url); // Setup a callback to be fired when a message or an event (open, close, error) is received webSocket.setOnMessageCallback([](const ix::WebSocketMessagePtr& msg) { if (msg->type == ix::WebSocketMessageType::Message) { std::cout << msg->str << std::endl; } } ); // Now that our callback is setup, we can start our background thread and receive messages webSocket.start(); // Send a message to the server (default to TEXT mode) webSocket.send(\"hello world\"); Why another library? There are 2 main reasons that explain why IXWebSocket got written. First, we needed a C++ cross-platform client library, which should have few dependencies. What looked like the most solid one, websocketpp did depend on boost and this was not an option for us. Secondly, there were other available libraries with fewer dependencies (C ones), but they required calling an explicit poll routine periodically to know if a client had received data from a server, which was not elegant. We started by solving those 2 problems, then we added server websocket code, then an HTTP client, and finally a very simple HTTP server. Contributing IXWebSocket is developed on GitHub . We'd love to hear about how you use it; opening up an issue on GitHub is ok for that. If things don't work as expected, please create an issue on GitHub, or even better a pull request if you know how to fix your problem.","title":"Home"},{"location":"#introduction","text":"WebSocket is a computer communications protocol, providing full-duplex and bi-directionnal communication channels over a single TCP connection. IXWebSocket is a C++ library for client and server Websocket communication, and for client and server HTTP communication. TLS aka SSL is supported. The code is derived from easywsclient and from the Satori C SDK . It has been tested on the following platforms. macOS iOS Linux Android Windows FreeBSD","title":"Introduction"},{"location":"#example-code","text":"// Required on Windows ix::initNetSystem(); // Our websocket object ix::WebSocket webSocket; std::string url(\"ws://localhost:8080/\"); webSocket.setUrl(url); // Setup a callback to be fired when a message or an event (open, close, error) is received webSocket.setOnMessageCallback([](const ix::WebSocketMessagePtr& msg) { if (msg->type == ix::WebSocketMessageType::Message) { std::cout << msg->str << std::endl; } } ); // Now that our callback is setup, we can start our background thread and receive messages webSocket.start(); // Send a message to the server (default to TEXT mode) webSocket.send(\"hello world\");","title":"Example code"},{"location":"#why-another-library","text":"There are 2 main reasons that explain why IXWebSocket got written. First, we needed a C++ cross-platform client library, which should have few dependencies. What looked like the most solid one, websocketpp did depend on boost and this was not an option for us. Secondly, there were other available libraries with fewer dependencies (C ones), but they required calling an explicit poll routine periodically to know if a client had received data from a server, which was not elegant. We started by solving those 2 problems, then we added server websocket code, then an HTTP client, and finally a very simple HTTP server.","title":"Why another library?"},{"location":"#contributing","text":"IXWebSocket is developed on GitHub . We'd love to hear about how you use it; opening up an issue on GitHub is ok for that. If things don't work as expected, please create an issue on GitHub, or even better a pull request if you know how to fix your problem.","title":"Contributing"},{"location":"CHANGELOG/","text":"Changelog All changes to this project will be documented in this file. [7.9.4] - 2020-01-12 (openssl + mbedssl) fix #140, can send large files with ws send over ssl / still broken with apple ssl [7.9.3] - 2020-01-10 (apple ssl) model write method after the OpenSSL one for consistency [7.9.2] - 2020-01-06 (apple ssl) unify read and write ssl utility code [7.9.1] - 2020-01-06 (websocket client) better error propagation when errors are detected while sending data (ws send) detect failures to send big files, terminate in those cases and report error [7.9.0] - 2020-01-04 (ws send) add option (-x) to disable per message deflate compression [7.8Line truncated
|
||||
+7
-7
@@ -2,37 +2,37 @@
|
||||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2019-12-25</lastmod>
|
||||
<lastmod>2020-01-13</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2019-12-25</lastmod>
|
||||
<lastmod>2020-01-13</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2019-12-25</lastmod>
|
||||
<lastmod>2020-01-13</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2019-12-25</lastmod>
|
||||
<lastmod>2020-01-13</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2019-12-25</lastmod>
|
||||
<lastmod>2020-01-13</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2019-12-25</lastmod>
|
||||
<lastmod>2020-01-13</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>None</loc>
|
||||
<lastmod>2019-12-25</lastmod>
|
||||
<lastmod>2020-01-13</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
Binary file not shown.
Reference in new issue
Block a user