messaging

I'm hoping that Ruby's message-passing infrastructure means there might be some clever trick for this. How do I determine the calling object -- which object called the method I'm currently in? As an option, there is a binding_of_caller gem that allows you to execute code in context of any caller on the call stack (caller, caller's caller and so on). It's useful for inspecting (read do anything at any position on the call stack ) call stack in development, as used in better_errors . Objects of class Binding encapsulate the execution context at some particular place in the code and retain this

Sending message to all client works well but I want to send message to particular username. my server.js file looks like. What it does is when http://localhost:8080 is run, the client code adds user to the object usernames as well as in socket object. And instantly returns the individual message to each of the connected client. //var io = require('socket.io').listen(8080); var app = require('http').createServer(handler) , io = require('socket.io').listen(app) , fs = require('fs') var usernames={}; app.listen(8080); // on server started we can load our client.html page function handler ( req,

I don't know why I'm having a hard time finding this, but I'm looking at some linux code where we're using select() waiting on a file descriptor to report it's ready. From the man page of select: select() and pselect() allow a program to monitor multiple file descriptors, waiting until one or more of the file descriptors become "ready" for some class of I/O operation So, that's great... I call select on some descriptor, give it some time out value and start to wait for the indication to go. How does the file descriptor (or owner of the descriptor) report that it's "ready" such that the select(

I'm looking for a small and yet efficient enough lightweight JMS broker solution with no or minimum of dependencies. My messaging code should be running in the environment with a lot of dependencies I have no control of. Thus it would make ridiculous to deploy say ActiveMQ solution along with my custom bunch of classes. nixau Currently I'm investigating FFMQ solution. It's open source (GNU LGPL license), has only 4 dependencies (commons-logging, log4j, jms and jmx), and it's mature enough to accomplish my goals. Especially if you're using spring, don't count activemq out. You can also run it

Suppose you have n processes, n > 2. You want to have agreement amongst them that one is to be active. So they need to vote amonst each other to determine which one is active. All processes may fail at any time, we want to have one process active if possible, but ... We must never have two active at the same time, so if they can't be sure it is better to have no-one active. (Ie. we want to avoid split brain) The only available communication mechanism between them is pub-sub messaging (not point to point). One or more databases are available, but no one database should be a single point of

I have difficulties wrapping my head around the concept. I am trying to implement an endpoint that listens on a tcp port for incoming messages in a proprietary format, which would then transform the message and have camel take over the forwarding and routing. Did I understand correctly that that the Producer is responsible for sending messages into the Endpoint and the Consumer receives them from that endpoint? When studying the interfaces I couldn't figure out the message flow between those objects, especially on the consumer part. Consumer only defines start() and stop() methods... When

I'm currently doing analysis and design for a new message bus architecture in my company. I have tried MSMQ to do something like this in the past and it works well and was thinking of doing the same thing again for this project but using WCF as the API instead of using the System.Messaging API. Has anyone had experience with MSMQ in WCF? Is it easier to use then the System.Messaging API? What would be some benefits of using WCF over System.Messaging or vice versa? Mauricio Scheffer IMHO, with so many good, flexible and proven bus architectures to choose from ( NServiceBus , Mass Transit ,