rfc
rfc copied to clipboard
zeromq
ZeroMQ RFC project
Seen in this README.md : ``` Specification lifecycle SHOULD follow the lifecycle defined in [COSS](http://rfc.unprotocols.org/spec:2/COSS) ``` The COSS link leads to "page not found".
If you'd like to help click that lovely green "Merge Pull Request" button, and get eternal karma, add a comment confirming that you've read and understand the C4 process at...
Builds for my PR earlier today and master once it was merged failed with the following message. ``` 1:31:19 PM: --------------------------------------------------------------------- UNSUPPORTED BUILD IMAGE The build image for this site...
Currently, the specifications of the messaging patterns define how these should behave but the main ZMTP specification defines the commands used by those messaging patterns. We could enhance the modularity...
The protocol specified in 37/ZMTP presents breaking changes in binary compatibility. (Subscribe/Unsubscribe messages versus Subscribe/Cancel commands.) The protocol specifies version downgrading at the level of the major version (cf. the...
It seems that since https://github.com/zeromq/rfc/pull/146, a lot of emphasis on thread-safety has been put into the specifications (37/ZMTP and the new messaging patterns. I don't understand why as I consider...
In the grammar for the ``cheezburger`` command there are two fields: `sequence` and `offset` with the same exact explanation: "File offset in bytes". In a command description `sequence` isn't even...
This I think can block us from changing the status of 3.1 to stable. I suggest to remove it from 3.1 and either move it to 3.2 or to its...
The prose contains this language: >All command bodies consist of an 8-character command name, padded with spaces, [...] This contradicts the ABNF immediately prior, in which command names are of...
The spec doesn't allow for arbitrary number of bytes, but it could be easily modified to handle it. In fact, there is enough information in just the `size` parameter to...
