Derek, I was throwing off examples, but you have to remember, ZeroMQ is NOT
just a replacement for a socket - it is a messaging library - a
full-fledged, cross-platform, cross-language,
high-performance, flexible scalable concise, messaging-tool-box, and it's
NOT just for networking, but also
And that's fine, but I still don't see the "need" for ZeroMQ in that
example. It's not adding websocket support to a non-real-time web-app. It's
only serving as the transport for messages from the webserver to the
websocket server. You could accomplish that just fine with a regular TCP
connecti
Here is an example for an architecture of using ZeroMQ for adding WebSocket
support to a non-real-time web-app, without much change to the existing
code (server is PHP in this case, but the architectural structure is what's
interesting)
http://socketo.me/docs/push
And here is a more in-depth a
On Thursday, April 11, 2013 10:57:44 AM UTC-7, Derek wrote:
>
> TCP is only the transport - you still have your application-specific
> protocols that you'd need to write. If your logstash gets a message like
> 'addlog "i like pizza" 07-11-2011' it doesn't know whether 'i like pizza'
> is an ap
TCP is only the transport - you still have your application-specific
protocols that you'd need to write. If your logstash gets a message like
'addlog "i like pizza" 07-11-2011' it doesn't know whether 'i like pizza'
is an application, a status, or a priority level. So ZeroMQ isn't going to
make
I thought about it, but I would have hopes someone with some experience with
web2py internals and perhapse with zmq would rise to the challange... I
wouldn't know even where to beging doing something like this myself..
--
---
You received this message because you are subscribed to the Google
Sounds to me like you have a couple of real life situations you need
solutions for. So the best thing to do is start coding. If you're unsure
about how to tackle the web2py integration, I'm sure people will provide
comments once you present your specific ideas or code drafts. If you start
out i
> I have no idea what you are trying to say there.
>
>
I am saying that there is an explosion of solutions for
every conceivable challenge, and the problem is that they are all
islands-onto-themselves - there is no standard way for application to
communicate with each other, and ZeoMQ could s
If you're talking about a webserver serving a database-backed website, I
see no need to use it. Perhaps some esoteric uses could be found for it.
On Wednesday, April 10, 2013 4:28:08 PM UTC-7, Massimo Di Pierro wrote:
>
> I really like 0MQ too but I would like to understand a typical test case
>
I think the more software will esit that has it buil-in, the more easy it
will become to build dynamically changing modular software infrastructures
I have no idea what you are trying to say there.
Anyway, yes, it's cool, you don't worry about message delivery because it's
completely out of yo
I really like 0MQ too but I would like to understand a typical test case of
integration with web2py. Consider the scheduler for example. The bottle
neck is not distribution of tasks (which 0MQ would handle great) but the
fact that tasks and main app need to access the database. If the workers do
11 matches
Mail list logo
