[zeromq-dev] what is the purpose of the Go binding for czmq?

[Andrew Hume]

brian, peter

	for what its worth, i have changed jobs and am now full-time developing Go
code using zeromq. in my last batch of zeromq code, i had switched from “plain”
zeromq to using czmq, and found that process quite satisfying. using the
improved (to my mind) API, and the various classes, simply made my code
smaller and easier to do.

	so i will be a willing guinea pig for go czmq, and should that not work out, then
i would happily drop back to zmq4.

	andrew

> On Jan 17, 2015, at 4:43 PM, Brian Knox <bknox at digitalocean.com> wrote:
> 
> Peter -
> 
> I am just now getting to a point that I am thinking about the "go-isms" that I want to build on top of the goczmq bindings myself (outside of channeler.go, which Luna contributed, which I've used in a small application now and I like).  I have some problems that I am working on solving at work, so I've got some real world issues I'm exploring.  I don't really have a set "plan" yet - things that I find that are useful to me, I'll add.  Things other people send as pull requests that are useful, I accept.  I anticipate that I'll experiment a lot and have some false starts - it's a learning experience.
> 
> I'll second what Pieter suggested - consider moving the bindings into the zeromq org, and try out the C4 process as a way to allow for low friction contributions.  We seem to have gathered together a small group of people with an interest in both go and zeromq at this point - with some cross pollination of ideas I bet we can have some fun and build some useful things!
> 
> Brian
> 
> 
> On Sat, Jan 17, 2015 at 5:47 PM, Peter Kleiweg <pkleiweg at xs4all.nl <mailto:pkleiweg at xs4all.nl>> wrote:
> Brian Knox schreef op de 17e dag van de louwmaand van het jaar 2015:
> 
> > Peter - really, it was more about wanting to see how czmq worked as the
> > basis for a language binding (since I contributed some code to czmq), than
> > anything particularly lacking in zmq4.
> 
> Ah, OK.
> 
> I'm a bit insecure. Unsure of what to do with zmq4. I started
> implementing zmq3 after reading about ZeroMQ and the current Go
> binding (which was mainly for ZeroMQ 2, and hard to adjust for
> version 3), and I thought I might have much use for a technology
> like ZeroMQ myself.
> 
> So I did zmq3, then zmq2. Then came version 4, and I did zmq4. I
> maintain all three versions. And when I add something to one
> version, I add it to the other versions as well, if possible.
> 
> And I implemented all the examples from the tutorial.
> 
> The thing is, I never actually got to using it myself. I have
> only one application running that has a PUB socket, and two apps
> with a SUB socket to the first app. Possibly the simplest of
> uses of ZeroMQ.
> 
> Now, I have forgotten most of what I learned by doing the
> tutorial. Still, I want to keep zmq2/3/4 up-to-date. But I don't
> actually know about using these techniques in real world,
> complex situations. What are recurrent patterns? Are there
> patterns that could be useful enough and general enough to
> include in the package?
> 
> After some discussion, I opened a wiki page for this stuff,
> demonstrations for how to do real world things with zmq4:
> 
> https://github.com/pebbe/zmq4/wiki/DesignPatterns <https://github.com/pebbe/zmq4/wiki/DesignPatterns>
> 
> I was hoping for contributions by people using zmq4, but until
> now, nothing.
> 
> 
> --
> Peter Kleiweg
> http://pkleiweg.home.xs4all.nl/ <http://pkleiweg.home.xs4all.nl/>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org <mailto:zeromq-dev at lists.zeromq.org>
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev <http://lists.zeromq.org/mailman/listinfo/zeromq-dev>
> 
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20150117/076cca1e/attachment.htm>