publish-subscribe

I've recently been asked to investigate the feasibility of integrating with a phone system vendor who wants to make phone events (e.g. line ringing, extension answered, call cleared) available using a RESTful web service. I pointed out that REST is a request/response protocol and they were doing publish/subscribe. The solution they were suggesting was to make an HTTP REST request which would block and then eventually respond if and when an event was available - or time out. Either way, another request would be made to get the next event and so on ad infinitum. This idea made me cringe, but I

I'm attempting to develop a social network that implements publisher-subscribe pattern (kind of like Twitter does): users can follow people, therefore being notified when a new publication of their followers is sent. All I have now is a working REST service implemented with JaxRS, running over Tomcat 7, offering services for login, register, getting profiles data and submitting posts. Servlet Mapping is done via web.xml My JaxRS app config RestServices Web.xml But the weight of the application comes from the pubsub part. And here is where things become messy. Before speaking of technologies

I'm trying to evaluate using Rx to create a sequence from a pub/sub pattern (i.e. classic observer pattern where next element is published by the producer(s)). This is basically the same as .net events, except we need to generalize it such that having an event is not a requirement, so I'm not able to take advantage of Observable.FromEvent. I've played around with Observable.Create and Observable.Generate and find myself end up having to write code to take care of the pub/sub (i.e. I have to write producer/consumer code to stash the published item, then consume it by calling IObserver.OnNext()

I'm trying to implement a simple Pub/Sub object in javascript, and here's my code: var PubSub=new function(){ this.subscriptions=[]; this.subscribe=function(topic,callback){ if(!this.subscriptions[topic]){ this.subscriptions[topic]=[]; } this.subscriptions[topic].push(callback); } this.unsubscribe=function(topic,callback){ if(this.subscriptions[topic]){ for(var i=this.subscriptions[topic].length-1;i>=0;i--){ if(this.subscriptions[topic][i]==callback){ this.subscriptions[topic].splice(i,1); } } } } this.publish=function(topic,data){ if(this.subscriptions[topic]){ for(var i=this.subscriptions

This is my first web application with WCF. So please guide me as a new guy. I'm trying to use WCF Callback to implement publish/subscribe pattern. I would like to send the message from UserA to UserB or UserA to every client at the moment. I got an example from here . In my app, I use ASP.NET as a client to connect WCF service instead and I found a problem when I subscribe to WCF service. The WCF service does not hold any other clients object. So when I call GetAllClients(_guid) , it will return only 1 client which is itself. Here is the code in ASP.NET page (I put every control inside

I need to build a system that is similar to a pub/sub system. It is composed of multiple sub-systems or services running in separate executables or as a Windows Services. The sub-systems are: The pub/sub service A pub/sub service managing communications between the internal sub-systems and the users. A user can have multiple channels open (A web page connected to a SignalR service, a mobile device connected to a duplex WCF service, etc.). The service should manage all the channels of an user and be able to send information to them on demand based on topics or specific users. The service must

Extended PUB/SUB topology I have multiple publishers and multiple subscribers in a use case with 1 intermediary. In the ZeroMQ guide, I learnt about synchronizing 1 publisher and 1 subscriber, using additional REQ/REP sockets. I tried to write a synchronization code for my use case, but it is getting messy if I try to write code according to logic given for 1-1 PUB/SUB . The publisher code when we have only 1 publisher is : //Socket to receive sync request zmq::socket_t syncservice (context, ZMQ_REP); syncservice.bind("tcp://*:5562"); // Get synchronization from subscribers int subscribers = 0