Found it, you can see us through the window
List of things to do:
dafka:
- how to make the API look like zmq's, accept zmq_msg_t type as input, how the receive looks like (topic), multipart support?
- mitch and match dafka sockets with zmq sockets
- router to distribute, or push to distribute, composable socket API
- persistence at both producer and consumer side
- partition naming, producer uuid: decouple?
- consumer only sends msg user if they know they have been stored?
libzmq:
- boring stuff
- relicensing
- new sockets:
- RFCs
- docs
- UDP: check asserts
- UDP: check ipv6
- poller: final PR zeromq/libzmq#2742
- make old/new sockets thread safe
- sub/unsub as command (zmpt 3.1)
- flacky tests - monitoring, test_system, many_sockets
- look at monitoring
- releases
- mailing list, update on the project
- performance regression tests: CI overbooked? azure vm?
- optimize curve, lots of data copies, curve_mechanism_base
- cmake support for TLS, websocket test
- cmake support multicast libnorm
- cool stuff:
- tcp zero copy recv/send
- avx optimisations for fast path decoder
- quic: cloudflare library MIT licensed
- websockets:
- docs
- boring stuff
- JSZMQ update API to match zeromq.js new APIs
List of things to do:
dafka:
- how to make the API look like zmq's, accept zmq_msg_t type as input, how the receive looks like (topic), multipart support?
- mitch and match dafka sockets with zmq sockets
- router to distribute, or push to distribute, composable socket API
- persistence at both producer and consumer side
- partition naming, producer uuid: decouple?
- consumer only sends msg user if they know they have been stored?
libzmq:
- boring stuff
- relicensing
- new sockets:
- RFCs
- docs
- UDP: check asserts
- UDP: check ipv6
- poller: final PR zeromq/libzmq#2742
- make old/new sockets thread safe
- sub/unsub as command (zmpt 3.1)
- flacky tests - monitoring, test_system, many_sockets
- look at monitoring
- releases
- mailing list, update on the project
- performance regression tests: CI overbooked? azure vm?
- optimize curve, lots of data copies, curve_mechanism_base
- cmake support for TLS, websocket test
- cmake support multicast libnorm
- cool stuff:
- tcp zero copy recv/send
- avx optimisations for fast path decoder
- quic: cloudflare library MIT licensed
- websockets:
- docs
- JSZMQ update API to match zeromq.js new APIs
Website:
- dafka and zyre add to zeromq.org
- migrate rfc.zeromq.org to hugo
- migrate from wikidot to github pages (or something else)
Zyre:
- DRAFT API, is it ready to be STABLE?
- https://echelog.com/logs/browse/zeromq/1578438000 to make a sort of distributed ccache using ZMQ technologies, which would allow discardable build nodes to benefit from a "library" of built objects shared by a persistent node (and feed objects into it) more easily than than using a general-purpose shared fliesystem like NFS.
So the UDP: check ipv6 is done: check here https://github.com/zeromq/libzmq/blob/master/unittests/unittest_udp_address.cpp
just arrived at the hackathon
So as a reference: "DRAFT API, is it ready to be STABLE?" We can't tell because we're not sure who's using it and whether they are happy with it. It seems some of the draft calls are perfectly fine. But we'd need someone who's using that to tell us. Last addition seems from oct 2019 and some draft methods are already there for a while (i.e. set_zcert() from 2017)
booked table at 8pm
I have a slight timing problem with passing by at 5PM, as I have to fetch my daughter at school on the other side of Brussels at 5PM
we can just close the door behind us
right?
anyone attended the KubeMQ webinar?
you can use the mailbox hole to clap the door