[zeromq-dev] Malamute broker project
Pieter Hintjens
ph at imatix.com
Sat Feb 28 19:48:13 CET 2015
Malamute could be used for discovery, yes. I'd probably want to add a
dedicated protocol for that, which includes certificate management (so
when you find a peer you can also get its public key from Malamute).
On Sat, Feb 28, 2015 at 6:39 PM, Kenneth Adam Miller
<kennethadammiller at gmail.com> wrote:
> Ah thanks so much! So yeah, I ran malamute right out of the source
> directory, and I'm having a hard time getting each side to receive the other
> sides messages. I know that messages are hitting the broker, but idk what's
> going on inside malamute itself. It spits out a failed security message,
> though I'm away from my computer I know it said null and plain in this
> message. So I thought I had to give it a username and password...
>
> I'll look up those docs when I get back home, I'm on a Starbucks break.
> Thanks!!!
>
> Also, I have some improvement ideas on increasing flexibility in that
> communication strategies can be made easily semmetric between client and
> broker as well as making the broker mutual party facilitation expand beyond
> just 2, to N number of different mutually requiring parties. Let me know if
> you want to hear.
>
> Basically, I'm wanting to use malamute to facilitate direct direct
> communications, so hosts exchange their known valid hostname through a
> broker mediated connection. At the point each opposite side gets it, it can
> call connect on the received string, and then communicate directly.
>
> On Feb 28, 2015 12:09 PM, "Pieter Hintjens" <ph at imatix.com> wrote:
>>
>> You can ignore the plain security method unless you want it (it gives
>> you a username/password check using ZeroMQ's PLAIN mechanism). The
>> malamute.cfg file enables this, you can however remove it when you
>> make your own configuration (or you can run the server without
>> external configuration file).
>>
>> I'll have some tutorials later for using Malamute. Take a look at
>> mlm_tutorial.c and mshell.c perhaps.
>>
>> On Sat, Feb 28, 2015 at 3:03 PM, Kenneth Adam Miller
>> <kennethadammiller at gmail.com> wrote:
>> > It's difficult to use the broker, even with the test that is included in
>> > the
>> > project tree. I am trying to write my own test just to try and exchange
>> > two
>> > strings between pairs of clients...
>> >
>> > In particular, I'm confused about this line:
>> > mlm_client_sendto (client, "server", "something", NULL, 1000, &msg);
>> >
>> > What is "server" or "something"? If the client is already connected, why
>> > do
>> > I need those two? Also,
>> >
>> > Also, what is "plain" security? I would like my packets to be just sent
>> > in
>> > the raw as I test... how do I get that? I'm using the malamute script
>> > that's
>> > in the src folder of the github repo.
>> >
>> > On Sat, Feb 28, 2015 at 6:25 AM, Bjorn Reese <breese at mail1.stofanet.dk>
>> > wrote:
>> >>
>> >> On 02/28/2015 08:29 AM, Doron Somech wrote:
>> >> > "HA is "single broker, designed to never crash" :-)"
>> >> >
>> >> > I more worried about hardware failure, specially when used in the
>> >> > cloud.
>> >>
>> >> Just run it on "hardware, designed to never fail" :-)
>> >>
>> >> _______________________________________________
>> >> zeromq-dev mailing list
>> >> zeromq-dev at lists.zeromq.org
>> >> 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
>> >
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> 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
>
More information about the zeromq-dev
mailing list