Morning,
On Sat, Mar 19, 2011 at 5:00 AM, Pieter Hintjens wrote:
> Robert,
>
> This is neat. It's something lots of people have discussed making but
> no-one's actually done.
>
Zed Shaw has a very nice implementation baked into the Mongrel2 web server (
http://mongrel2.org/home).
It uses a PUS
On Saturday 19, Pieter Hintjens wrote:
> Robert,
>
> This is neat. It's something lots of people have discussed making but
> no-one's actually done.
>
> Presumably this gives us security over HTTPS, and makes 0MQ accessible
> to JavaScript clients.
The HTTP server in lua-handlers supports HTTPS
Robert,
This is neat. It's something lots of people have discussed making but
no-one's actually done.
Presumably this gives us security over HTTPS, and makes 0MQ accessible
to JavaScript clients.
One thing I'm wondering, if we can make a formal specification for
what 0MQ-over-HTTP (and HTTP-over
On Sat, Mar 19, 2011 at 12:06 PM, Vijay Mathew
wrote:
> I have started working on a ZeroMQ binding for Pharo.
> (http://www.pharo-project.org/home).
Very nice! If you want to provide Pharo examples, I'd suggest
translating some / all of the examples from the Guide into Pharo.
These can also act
Hi all,
I have created a simple HTTP to 0MQ proxy [1] written in 150 lines of Lua
code. It uses the async. HTTP server & 0MQ socket handlers from my lua-
handlers [2] project.
When a HTTP POST request is received it allocates a unique request id and
sends the POST data to a XREQ socket with a
Hi all,
I have started working on a ZeroMQ binding for Pharo.
(http://www.pharo-project.org/home).
Thanks,
-- Vijay
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
sust...@250bpm.com said:
> On 03/18/2011 02:09 PM, Martin Lucina wrote:
>
> > What do you think? This approach would provide the name lookup without the
> > need for any external service.
>
> Why not simply write auto-generated port number to the file provided in
> the connection string? The oth
On 19 March 2011 16:41, Martin Sustrik wrote:
> As a side note: The patch seems to mix several issues. AFAICS aside of
> HTTP thing, there's some logging functionality, some PGM related changes
> etc.
>
>
The HTTP side is a bit weird, the code follows basic 1.0 paradigm but
requests version 1.1.
Hi Vyacheslav,
> Here are changes to support HTTP protocol while transferring messages
> throw the TCP socket.
>
> https://github.com/zeromq/zeromq2-1/pull/12
>
> I've added http_socket_t class which is derived from tcp_socket_t.
> For now zmq_engine_t creates desired socket instance depending on
Martin,
Please find attached a patch for these changes. It's mostly the
zmq_socket(3) man page that changed.
-Pieter
From 42c672aa781c3230ce2240f205eb924074c25a1c Mon Sep 17 00:00:00 2001
From: Pieter Hintjens
Date: Sun, 13 Mar 2011 06:54:57 +0100
Subject: [PATCH] Defined ZMQ_DEALER and ZMQ_ROUT
On Sat, Mar 19, 2011 at 9:19 AM, Martin Sustrik wrote:
> Let's wait couple of days and if there's no considerable opposition let's
> pull it into the master.
I'll send the patch then, you can merge it if/when you like.
-Pieter
___
zeromq-dev mailing l
On Sat, Mar 19, 2011 at 9:11 AM, Martin Sustrik wrote:
>> It does seem to work. What are the bugs and unfinished areas you're
>> thinking of?
> See following issues...
They're old issues, suggesting that part of the problem is circular.
People won't use broken code that doesn't evolve, thus no-o
On 03/19/2011 09:14 AM, Pieter Hintjens wrote:
> Martin, I am making this change for 2.1, because there was consensus
> on the change, and the old names are simply too painful to keep using.
> If you like I'll provide you a patch for it. I've not renamed the
> source files, but presumably that wou
On Sat, Mar 19, 2011 at 9:07 AM, Martin Sustrik wrote:
> Thus, if we add a following line to zmq.h:
> #define ZMQ_ROUTER ZMQ_XREP
> we can achieve 3 goals in parallel...
Note that the original problem, and why I invented the "ROUTER"
nomenclature, was a pure *documentation* issue, similar to the
On 03/19/2011 09:03 AM, Pieter Hintjens wrote:
> It does seem to work. What are the bugs and unfinished areas you're thinking
> of?
See following issues:
https://github.com/zeromq/zeromq2/issues#issue/3
https://github.com/zeromq/zeromq2/issues#issue/4
https://github.com/zeromq/zeromq2/issues#is
On Fri, Mar 18, 2011 at 4:00 PM, Вячеслав Мурашкин
wrote:
> Here are changes to support HTTP protocol while transferring messages throw
> the TCP socket...
Вячеслав,
Thanks for this interesting contribution. The 2.1 branch is only
accepting bug fixes and cleanups, so you'll have to submit a pat
Hi Andrew,
> it is interesting to see such a multi-level discussion!
> (and it is rewarding to see how much of this is driven by how successful
> 0mq is!)
> let me offer some observations:
>
> 1) the rasion d'etre, or central meme, of 0mq is scalability to
> internet-sized problems.
> no one else
On Sat, Mar 19, 2011 at 8:54 AM, Martin Sustrik wrote:
> However, it is unfinished, buggy and basically unmaintained, so it would be
> good if those using it would at least start the discussion about how to
> finish it properly.
So the main use case I've found is connecting pairs of threads over
Hi Pieter,
>> Btw, anyone out there using ZMQ_PAIR anymore? What about dropping it in
>> 3.0? Hearing Zed Shaw saying something like "I don't know how to use it.
>> I've never used a pair socket myself," makes me hope that that's the case.
>
> Well, as far as I can tell there are proper use cases
FYI
-- Forwarded message --
From:
Date: Fri, Mar 18, 2011 at 7:59 PM
Subject: Thank you for your application
To: martin.sust...@gmail.com
Hi Martin Sustrik,
Thank you for submitting "ZeroMQ" organization application to Google Summer
of Code 2011. Unfortunately, we were unable
On Friday 18, Вячеслав Мурашкин wrote:
> Here are changes to support HTTP protocol while transferring messages throw
> the TCP socket.
>
> https://github.com/zeromq/zeromq2-1/pull/12
>
> I've added http_socket_t class which is derived from tcp_socket_t.
> For now zmq_engine_t creates desired sock
Here are changes to support HTTP protocol while transferring messages throw
the TCP socket.
https://github.com/zeromq/zeromq2-1/pull/12
I've added http_socket_t class which is derived from tcp_socket_t.
For now zmq_engine_t creates desired socket instance depending on
options_t::proto value.
Cla
22 matches
Mail list logo
