{"action":"created","issue":{"url":"https://api.github.com/repos/methodmissing/rbczmq/issues/35","labels_url":"https://api.github.com/repos/methodmissing/rbczmq/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/methodmissing/rbczmq/issues/35/comments","events_url":"https://api.github.com/repos/methodmissing/rbczmq/issues/35/events","html_url":"https://github.com/methodmissing/rbczmq/issues/35","id":56458855,"number":35,"title":"Support for CZMQ 3.x?","user":{"login":"colstrom","id":469456,"avatar_url":"https://avatars.githubusercontent.com/u/469456?v=3","gravatar_id":"","url":"https://api.github.com/users/colstrom","html_url":"https://github.com/colstrom","followers_url":"https://api.github.com/users/colstrom/followers","following_url":"https://api.github.com/users/colstrom/following{/other_user}","gists_url":"https://api.github.com/users/colstrom/gists{/gist_id}","starred_url":"https://api.github.com/users/colstrom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/colstrom/subscriptions","organizations_url":"https://api.github.com/users/colstrom/orgs","repos_url":"https://api.github.com/users/colstrom/repos","events_url":"https://api.github.com/users/colstrom/events{/privacy}","received_events_url":"https://api.github.com/users/colstrom/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-02-04T00:01:49Z","updated_at":"2015-02-04T00:52:06Z","closed_at":null,"body":"I'm curious what the status of CZMQ 3.x support is in rbczmq. I'm interested in working with some of the classes introduced in 3.x (specifically zactor and zgossip). If support is non-trivial to add (I haven't done much with FFI, so I'd rather not assume anything about complexity), is there anywhere that I could focus my time to assist?\r\n\r\nOn a related tangent, it looks like ffi-rzmq has gone into maintenance-only mode (within the last week or so) in favour of this project. It looks like rbczmq is the left as the main library for developing (C)ZMQ-based applications in Ruby. Exciting! ^_^"},"comment":{"url":"https://api.github.com/repos/methodmissing/rbczmq/issues/comments/72769321","html_url":"https://github.com/methodmissing/rbczmq/issues/35#issuecomment-72769321","issue_url":"https://api.github.com/repos/methodmissing/rbczmq/issues/35","id":72769321,"user":{"login":"colstrom","id":469456,"avatar_url":"https://avatars.githubusercontent.com/u/469456?v=3","gravatar_id":"","url":"https://api.github.com/users/colstrom","html_url":"https://github.com/colstrom","followers_url":"https://api.github.com/users/colstrom/followers","following_url":"https://api.github.com/users/colstrom/following{/other_user}","gists_url":"https://api.github.com/users/colstrom/gists{/gist_id}","starred_url":"https://api.github.com/users/colstrom/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/colstrom/subscriptions","organizations_url":"https://api.github.com/users/colstrom/orgs","repos_url":"https://api.github.com/users/colstrom/repos","events_url":"https://api.github.com/users/colstrom/events{/privacy}","received_events_url":"https://api.github.com/users/colstrom/received_events","type":"User","site_admin":false},"created_at":"2015-02-04T00:52:06Z","updated_at":"2015-02-04T00:52:06Z","body":"Sounds like a sane plan. A 10km view of the changes looks something like this:\r\n\r\nIt looks like `zauth`, `zbeacon`, `zmonitor`, `zproxy`, and `zthread` were merged into **`zactor`**. Since those usually got bundled anyways, that's a cleaner expression of intent for a lot of cases. They haven't been removed, though they are deprecated. That should make the transition somewhat easier.\r\n\r\n`zctx` and `zsocket` were deprecated in favour of the new context-less **`zsock`**, which is a nice improvement from a Ruby perspective (contexts always felt like C-isms seeping into Ruby). Along with this is deprecation of `zsockopt` in favour of **`zsock_option`** meant to play nice with `zsock`.\r\n\r\n`zmutex` is deprecated now, I assume since it was primarily useful with the also-deprecated `zthread`.\r\n\r\nThere are a few new items, **`zgossip`** intends to address service-discovery problems, and looks useful in propagating configuration state changes as well.\r\n\r\nThe release notes mention a **`zrex`** class for regular expressions? I have no idea what the intended use case is for that. Seems a bit out-of-scope for ZMQ's problem domain, but I haven't looked at it closely, so I could be a completely sensible use and I may just be talking out my ass.\r\n\r\nI can look at cooking up some example docs, and I'll take a skim over the existing documentation to see where it needs the most love. Is there a preference for more implementation-focused (RDoc/YARD-style) or more example-driven with documentation of why user X might care about the functionality they're reading about? I guess I'm trying to identify the audience of the missing docs.\r\n\r\nAs for the security API additions, they don't seem tightly coupled with 3.x (they seem to be carried forward from 2.x). Important, but might be easier to implement without the API shifting underneath them."}}