A mirror of https://github.com/nanomsg/nng https://cogarr.net/source/cgit.cgi/nng/atom?h=v1.0.0-beta.2 2018-05-22T18:21:29Z 2018-05-22T18:21:29Z Garrett D'Amore garrett@damore.org 2018-05-22T18:21:29Z urn:sha1:96ef8d6535f6980e0ce667b7659747a98a875ab6 2018-05-22T18:18:41Z Garrett D'Amore garrett@damore.org 2018-05-22T18:18:41Z urn:sha1:7cd6e3a54c8bff4a008b324e310ae3cfcaa3ebf1 2018-05-22T17:29:06Z Garrett D'Amore garrett@damore.org 2018-05-22T17:27:47Z urn:sha1:959eabe2675a3b8be9bc2b2459cc899a5a64b283 fixes #464 Support NN_WS_MSG_TYPE option (compat) fixes #415 websocket does not honor recv maxsize This fixes a significant (and security) issue in websocket, where the code does not honor a maximum receive size. We've exposed new API (internal) to set the limit on the frame size, and we've changed the default to *unlimited* for that internal API. (But the default for SP sockets, which are the only consumers at present, is still 1MB just like all other SP transports.) 2018-05-22T04:27:16Z Garrett D'Amore garrett@damore.org 2018-05-22T04:19:20Z urn:sha1:67f5ed6e5c0dd7bdd9002bbb519ab34f35fef8dd 2018-05-22T04:27:16Z Garrett D'Amore garrett@damore.org 2018-05-21T23:49:31Z urn:sha1:a3cf238a431e6a454f43a66f3c02a2f17d6dfc61 2018-05-22T04:27:16Z Garrett D'Amore garrett@damore.org 2018-05-21T22:51:08Z urn:sha1:d0cf8ce6f43daf6882037dbdcdaa7f2169dd1e6a fixes #468 TCP nodelay and keepalive should start usable fixes #467 NN_RCVMAXSZ option does not work (compat) fixes #465 Support NN_OPT_TCPNODELAY (compat) This is a rather larger change set than I'd like, but when adding support for legacy TCP keepalive, I found a number if issues using the legacy TCP test (which we are introducing with this commit.) This fixes the concerns that are relevant and addressible. We have elected not to try to support to local address binding at this time, and the IPv6 test case in the old code was wrong, so changes relevant to that are commented out. I've also updated the nng_compat manual page to reflect additional caveats that folks should be aware of, including the previously undocumented caveat around the NN_SNDBUF and NN_RCVBUF options. 2018-05-22T04:27:13Z Garrett D'Amore garrett@damore.org 2018-05-22T02:14:48Z urn:sha1:45692d50c33f1fbc45554a5b82281046c4b3621a 2018-05-21T20:58:42Z Garrett D'Amore garrett@damore.org 2018-05-21T20:58:42Z urn:sha1:e7b81a00dcf1184275aa2b2b40badba3dac990b7 2018-05-21T20:52:18Z Garrett D'Amore garrett@damore.org 2018-05-19T17:33:11Z urn:sha1:b2c9baba988347c5bf15423f2ea40ce9d05da075 As part of this code fix, we needed to add filtering support to the msgq_tryput code path -- it turns out that code path was bypassing the filterfn altogether. Eventually we'll remove all this filtering stuff from the msgq code and replace it with inline filtering directly in sub. 2018-05-21T20:28:56Z Garrett D'Amore garrett@damore.org 2018-05-21T20:27:06Z urn:sha1:6abb328523509d35663f54ee0012254232df4a0a I actually made these real headers, not stubs While here I made some improvements to the nng_compat man page, to improve the language and also the presentation on some devices. (We were going nuts with the icons, instead, I've made a single new section, called Caveats, that lists a bunch of them.) This should not have any impact on binary compatibility.