On Thu, Jan 9, 2014 at 8:24 AM, crocket crockabisc...@gmail.com wrote:
Nowadays, almost every city is covered with WiFi hotspots.
And, almost every modern building and meetup is covered well by WiFi
hotspots.
Most houses have a hotspot or two.
Why don't we take advantage of existing WiFi
On Thu, Jan 9, 2014 at 7:50 AM, Laurent Alebarde l.aleba...@free.fr wrote:
And a 4th one: have the security protocol (CURVE or PARANO) build on top of
libzmq or czmq. They would simply use the libzmq default mechanism NULL.
That is what libcurve does.
BTW, what are the pros/cons to have a
Thanks a lot Pieter (I missed your 23:44 message - sorry).
Le 09/01/2014 09:08, Pieter Hintjens a écrit :
On Thu, Jan 9, 2014 at 7:50 AM, Laurent Alebarde l.aleba...@free.fr wrote:
And a 4th one: have the security protocol (CURVE or PARANO) build on top of
libzmq or czmq. They would simply
The main reason for not just using push_back was that I was unsure how
shifting the message when vectors went over capacity would effect the
zmq_msg_t structures. I've since wrapped the whole lot in a frame object
that handles it and now does just use push_back. (see
Just connect to Zurl's REQ-handling endpoint (by default, tcp port 5553)
and send a tnetstring-formatted message. You can find a tnetstring PHP
library here: https://github.com/phuedx/tnetstring (note, I've not tried
this, as I'm not a PHP developer).
To make an HTTP request, send a message
Oh, and the message you send must be prefixed with a capital 'T'
character. Byte 0 is a T, and byte 1 is the start of the
tnetstring-formatted payload.
On 01/09/2014 01:26 AM, Justin Karneges wrote:
Just connect to Zurl's REQ-handling endpoint (by default, tcp port 5553)
and send a
On 01/09/2014 09:06 AM, Pieter Hintjens wrote:
* Many public hotspots, especially in the US, block client-to-client traffic.
If you are talking about wireless isolation, then they only block
multicasting. This means that you cannot discover other devices, but
if you happen to know their IP than
On Jan 9, 2014, at 10:52, Bjorn Reese bre...@mail1.stofanet.dk wrote:
On 01/09/2014 09:06 AM, Pieter Hintjens wrote:
* Many public hotspots, especially in the US, block client-to-client traffic.
If you are talking about wireless isolation, then they only block
multicasting. This means
On Thu, Jan 9, 2014 at 12:19 PM, Bruno D. Rodrigues
bruno.rodrig...@litux.org wrote:
On Jan 9, 2014, at 10:52, Bjorn Reese bre...@mail1.stofanet.dk wrote:
If you are talking about wireless isolation, then they only block
multicasting. This means that you cannot discover other devices, but
if
No problem. The project you want is here: https://github.com/zeromq/libcurve
On Thu, Jan 9, 2014 at 9:27 AM, Laurent Alebarde l.aleba...@free.fr wrote:
Thanks a lot Pieter (I missed your 23:44 message - sorry).
Le 09/01/2014 09:08, Pieter Hintjens a écrit :
On Thu, Jan 9, 2014 at 7:50 AM,
I am a new user. I just compiled the c Majordomo example and run it in my
development laptop. It ran successfully but was extremely slow.
~/gitzguide/zguide/examples/C$ time ./mdclient
10 requests/replies processed
real1m8.093s
user0m8.224s
sys0m8.872s
Has anyone experienced this
Can manual assistance be effective in case of anonymous/pseudonomous
broadcast used in async message apps?
On Jan 9, 2014 3:05 PM, Pieter Hintjens p...@imatix.com wrote:
On Thu, Jan 9, 2014 at 1:32 AM, crocket crockabisc...@gmail.com wrote:
Until there comes the edgenet mailing list, we can
Hey there,
We are currently doing research for our project to figure out the best
way to do inter-thread communication with a message queue. As we are
using zmq for networking purposes already, it was logical to also
research it for the above purpose.
Now, we will have a number of threads
My idea was to make it like a game: by finding and peering with other
devices you gain points. It is very close to deliberate peering with
people you actually know. The two cases may overlap.
On Thu, Jan 9, 2014 at 2:13 PM, crocket crockabisc...@gmail.com wrote:
Can manual assistance be
The documentation recommends creating one single context per process,
and when creating it you specify how many zeromq threads to use.
--
Bruno Rodrigues
Sent from my iPhone
No dia 09/01/2014, às 13:33, Jan Drabner j...@jdrabner.eu escreveu:
Hey there,
We are currently doing research for
Bluetooth works well enough as a standard network interface bnep0 if the
messages you're sending are small. (It really is pretty slow, though.) The
hard part is programmatically configuring the stack to use it that way, and
(preferably) programmatically pairing without user interaction.
On Thu,
There really is no cost to using a smartphone as hotspot except a
little delay and some battery life, while switched on.
Battery life may be more of an issue than you realize. Wifi radios use far
less power than 3G radios, but they still *do* use power, and the pattern
of network activity can
For inproc you don't need any I/O threads at all. The default will be
1 additional thread per context, so as Bruno says, per process.
On Thu, Jan 9, 2014 at 2:33 PM, Jan Drabner j...@jdrabner.eu wrote:
Hey there,
We are currently doing research for our project to figure out the best
way to do
Ad-hoc mode is too poorly supported to depend on. And it's slow.
In any case a phone cannot act as a hotspot for any length of time. On
some firmwares enabling AP mode will switch off 3G. This is still fine
for us. My idea was to put this decision at the user level, initially.
The application
If you don't trust your peers you should probably be using ZeroMQ 4.x
and security. Then you will only see authenticated peers.
On Wed, Jan 8, 2014 at 12:32 PM, Dmitriy Vsekhvalnov
dvsekhval...@gmail.com wrote:
Hi All,
continue my little evaluation of zeromq and wanted to ask next question: is
Having no experience on the matter, why not use bluetooth as an interface
that searches for peers and wifi for real network traffic.
Wifi will be switched on only when there is need for data to be sent.
That could also help the wifi automatically switch to the best access point.
Bluetooth has a
I imagine you've figured it out by now, but just in case
When a vector method needs to reallocate the underlying array, existing
elements are move-constructed onto the new memory. If no move constructor
is defined or if you are not using C++11 mode, they will be
copy-constructed instead.
In the short term that may be the only solution that's workable without
root access on at least some of the phones. I think the full benefits of
EdgeNet won't be realized until arbitrary phones can serve as routers or
data mules without the user knowing or caring, though.
I still think WiFi
I'd like to. But it doesn't seem to be possible with Java or CLR at the
moment. And we don't have time/budget to invest in support right now.
Thanks for answer.
On Thu, Jan 9, 2014 at 6:19 PM, Pieter Hintjens p...@imatix.com wrote:
If you don't trust your peers you should probably be using
After much head-banging, valgrinding, I've finally identified the problem.
Since msg stores the zmq_msg_t objects in a vector, and small enough
messages are stored directly in the zmq_msg_t rather than by pointer,
calling raw_new_msg() was actually invalidating some of the pointers I have
On Thu, Jan 9, 2014 at 3:55 PM, Lindley French lindl...@gmail.com wrote:
In the short term that may be the only solution that's workable without root
access on at least some of the phones. I think the full benefits of EdgeNet
won't be realized until arbitrary phones can serve as routers or
JZMQ runs on ZeroMQ v4.0 and supports the security layers.
On Thu, Jan 9, 2014 at 5:03 PM, Dmitriy Vsekhvalnov
dvsekhval...@gmail.com wrote:
I'd like to. But it doesn't seem to be possible with Java or CLR at the
moment. And we don't have time/budget to invest in support right now.
Thanks for
In case anyone tries this, a recent update from Microsoft has some how
blocked this combination and causes a new unique error message:
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(58,5):
error MSB8032: The Platform or PlatformToolset is not available from
http://developer.android.com/guide/topics/connectivity/wifip2p.html tells
android has WiFi Direct capability since 4.0.
This is a good news. I'm not sure about iOS, but iPhones can connect
to WiFi-Direct-capable android phones.
On Fri, Jan 10, 2014 at 5:31 AM, Pieter Hintjens p...@imatix.com
Plus, I tested my nexus 5 and 7 with Super Beam app.
Super Beam shares files and folders using WiFi Direct.
My nexus devices successfully shared files via WiFi Direct.
WiFi Direct is confirmed to be working at least on nexus devices.
On Fri, Jan 10, 2014 at 5:31 AM, Pieter Hintjens
Dear list,
I’m looking at using the STREAM socket to interface with some plain old TCP
clients, however, there seems to be two things I’m missing:
1. How do I send a message to a client first? Once the client sends a message I
can get the identity frame and use that to reply. How do I send a
In CZMQ and PYZMQ you can use the socket event monitor interface to receive
socket event notification of things such as connect, disconnect, accepted,
etc.
I use the zmonitor from CZMQ and zmq.utils.monitor.recv_monitor_message
from pyzmq for receiving connection state information in applications
32 matches
Mail list logo
