brian,
maybe this is a setup issue.
when i run it, the received beacon is empty, and the listener only returns
after the timeout expires. (i changed the timeout to 5s to help debug this.)
so i deduce the listener never gets what the publisher sends.
can there be firewalls or some other networking crap interfering with this?
> On Jan 18, 2015, at 4:29 AM, Brian Knox <[email protected]> wrote:
>
> Andrew: what is actually published is the IP address of the beacon = so the
> "HI" in the example is a topic, and not what is actually received. So, the
> publisher is publishing on topic "HI", and the subscriber is subscribing on
> topic "HI". Running locally:
>
> ./b
> Beacon configured on: 192.168.1.199
> Beacon configured on: 192.168.1.199
> Received beacon: 192.168.1.199
>
> I'll fix the example code to the new function names, thanks for catching
> that. Awhile back, we removed the "Z" prefixes from everything as they
> weren't necessary in a language that has package namespaces.
>
> Brian
>
>
> On Sun, Jan 18, 2015 at 12:17 AM, Andrew Hume <[email protected]
> <mailto:[email protected]>> wrote:
> brian,
>
> i copied the zbeacon example from the github site and ran it.
> (i had to change NewZbeacon to NewBeacon.)
>
> it doesn’t work, in that listener.Recv is always returning an empty string
> regardless of what is published.
>
> so either i don’t understand what is supposed to happen, or there is a bug
> somewhere.
>
> _______________________________________________
> zeromq-dev mailing list
> [email protected] <mailto:[email protected]>
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> <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
