Despite the fact that Context looks like an empty binary, it represents a native resource which is not empty, and whose inspection in Erlang shell is meaningless. See this: http://erlang.2086793.n4.nabble.com/question-about-NIF-resources-tt3171272.html#none
On Wed, Sep 4, 2013 at 4:36 AM, Michael Scofield <[email protected]>wrote: > OH...I should have definitely checked the syntax. > But, why is > {ok, Context} = erlzmq:context(). > the Context is empty? Shouldn't it be some zeromq context > handler/reference? > > > 2013/9/4 Pieter Hintjens <[email protected]> > >> The correct syntax would be "tcp://*:5555" (note the extra ':') >> >> On Wed, Sep 4, 2013 at 8:37 AM, Michael Scofield <[email protected]> >> wrote: >> > Hi: >> > I've just install the erlzmq2 on my laptop(Ubuntu 12.04 32bit). >> > I decided to try it. So I opened the erl shell, and tried this: >> > {ok, Context} = erlzmq:context(). >> > It returned >> > {ok,<<>>} >> > Something was not right here: the Context were just empty bits! >> > Then I continued: >> > {ok, Responder} = erlzmq:socket(Context, rep). >> > erlzmq:bind(Responder, "tcp://*5555"). >> > here came the error when the last statement was executed: >> > {error, einval} >> > How such error happened? >> > >> > _______________________________________________ >> > zeromq-dev mailing list >> > [email protected] >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > >> _______________________________________________ >> zeromq-dev mailing list >> [email protected] >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev >> > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
