meteor,publish-subscribe,meteor-collections
I think you are getting [] because you are publishing the data on the startup, when isn't ready, lets make that subscribe reactive. Tracker.autorun(function(){ Meteor.subscribe("states", function(){ console.log(states, states.find(), states.find().fetch()); }); }); OPTIONAL There is no reason to declare the collections inside the isServer/isClient if statements Since you are starting with...
mongodb,collections,meteor,publish-subscribe,meteor-accounts
You're not supposed to change the root fields of the user object: Meteor.users.update(user, {$set: {"profile.currentHotel": "something"}}); Read more here: http://docs.meteor.com/#/full/meteor_users...
python,asynchronous,zeromq,publish-subscribe,python-asyncio
The issue is that you're trying to yield from the call to self.stream.write(), but stream.write isn't actually a coroutine. When you call yield from on an item, Python internally calls iter(item). In this case, the call to write() is returning None, so Python is trying to do iter(None) - hence...
c#,asp.net,asp.net-web-api,signalr,publish-subscribe
There are lots of ways of designing pub / sub around SignalR I created a wrapper for SignalR to solve it in a Event aggregation form Please see the wiki https://github.com/AndersMalmgren/SignalR.EventAggregatorProxy/wiki Install using nuget Install-Package SignalR.EventAggregatorProxy See the demo project https://github.com/AndersMalmgren/SignalR.EventAggregatorProxy/tree/master/SignalR.EventAggregatorProxy.Demo.MVC4...
asp.net,redis,html-table,real-time,publish-subscribe
For anyone, who might stumble onto this. I finally managed to do it by storing the most recent value from the subscription in a Redis key value pair (Hset), and then ran an AJAX call to retrieve that value in a loop. A list can also be used if you...
java,javascript,publish-subscribe,pubnub
I figured out that we had to enable Presence feature for each key on the PubNub dashboard for this to work. Silly thing I missed out..
If you have a close look at the docs for subscribe, you'll find this note in a section about reactive computations: However, if the next iteration of your run function subscribes to the same record set (same name and parameters), Meteor is smart enough to skip a wasteful unsubscribe/resubscribe. So...
sorting,meteor,publish-subscribe
As David mentioned below I do needed sorting on the client so I hold on to that and tried some different directions using my publication to achieve some sort of partial reactivity on the client. I ended up implementing a publication with an observeChanges pattern and sort on lastactivity on...
You have two correct answers but they do assume some knowledge for you. Here's what it looks like using Meteor's file structure (available at http://docs.meteor.com/#/full/structuringyourapp). In your /lib (shared) directory Make a file called "collections.js" and in it create your collection. userFriends = new Mongo.Collection("friends"); I would instead do userFriends...
servlets,publish-subscribe,g-wan
G-WAN already provides a simple publisher/subscriber engine, see the Comet servlet example. This works fine with slow (typically 1 update per second) feeds. For real-time and BigData feeds, there's no alternative to using G-WAN protocol handlers (to bypass connection handler rewrites and to precisely define the desired latency). That's what...
ruby-on-rails,postgresql,publish-subscribe,pubnub
Why not use our History API, and leave the storage to us? ;) https://www.pubnub.com/docs/ruby/api/reference.html#history...
You can push directly to your mobile topic subscribers. Take a look at GCM PubSub: https://developers.google.com/android/reference/com/google/android/gms/gcm/GcmPubSub
javascript,jquery,oop,publish-subscribe
You're on the right track. This is the simple and clear example given from the jQuery API Docs for handling custom events: $( "#foo" ).on( "custom", function( event, param1, param2 ) { alert( param1 + "\n" + param2 ); }); $( "#foo").trigger( "custom", [ "Custom", "Event" ] ); Also cleaned...
Ok I got the problem. I created a local subscriber, which always was deleted if the program leaved the method. So simple but so fatal. Now I create a object variable and it works....
design-patterns,websocket,publish-subscribe,autobahn
Ideally, I would want for the publisher to notice that I just subscribed and push the initial value to the individual client This is a pefectly fine use case and desired behavior .. in fact, it's on the feature list for the WAMP Advanced Profile: https://github.com/tavendo/WAMP/issues/69 This seems sufficiently...
javascript,node.js,webrtc,publish-subscribe,pubnub
WebRTC Signaling Exchanging ICE Candidates via PubNub The goal is to exchange ICE candidate packets between two peers. ICE candidate packets are structured payloads which contain possible path recommendations between two peers. You can use a lib which will take care of the nitty gritty such as http://www.sinch.com/ and below...
javascript,requirejs,publish-subscribe,mediator
I would just minimally break the DRY principle and have cat, for instance, like this: define(['animalFactory!cat'],function(animalInstance){ animalInstance.sound === 'meow'; // should be true }); The fact of the matter is while it would be possible to do what you want using a loader, the resulting code would be complicated, and...
templates,meteor,publish-subscribe
You could use a reactive computation inside your onCreated lifecycle event. Template.test.onCreated(function () { this.autorun(function(){ var currentRouteParamId = Router.current().params._id; this.subscribe('mydata', currentRouteParamId); }.bind(this)); }); Router.current() being a reactive data source, the inner reactive computation setup by this.autorun will rerun whenever the current route is modified via navigation. Subscriptions calls made inside...
java,publish-subscribe,qos,dds
Why you see what you see: You are using Subscriber.DATAREADER_QOS_DEFAULT and Publisher.DATAREADER_QOS_DEFAULT, and the 'is_default_qos' boolean is set on the Keep_Last depth 1 profile. What it is doing under the hood: When you have is_default_qos flag set on profile "Foo", THAT is the profile that will be used, when you...
heroku,websocket,out-of-memory,publish-subscribe,faye
Ok, I realised the mistake. I was creating the client outside the EM.run block. Once i moved the initialization inside the EM.run block, everything was working fine....
javascript,design-patterns,refactoring,publish-subscribe
There are several approach to achieve this kind of thing. Based on your architecture, requirements, preference you can do either of the following: Approach 1 : You can accept a callback function as a init function and there you can handle it. var library = function(initCallback) { ev.subscribe('init', initCallback); //library...
Efficiency would be to use multicasting UDP as means of transport: several subscribers listen to one "stream". http://docs.oracle.com/javase/tutorial/networking/datagrams/broadcasting.html as transport protocol to send 1 thing to several recipients. To achieve that in an orchestrated way, a subscriber maybe first has to announce himself and receive a start time, and decryption...
javascript,mongodb,collections,meteor,publish-subscribe
Don't use Meteor.publish for searching. Create a Meteor.method on the server instead to find the search results. Create a client-only (unmanaged) collection var results = new Mongo.Collection(null) When you perform the search, remove all results results.remove({}) and then insert the results from the Meteor.method callback. Then, to stop each search...
c++,websocket,publish-subscribe,libwebsockets
found it! libwebsockets lets you broadcast to all connected users to a specific protocol using libwebsocket_callback_on_writable_all_protocol(*protocol) which triggers LWS_CALLBACK_SERVER_WRITEABLE that will be handled by the protocol's callback function and that's where we could send the data. So, typically, I use my second protocol (the non-http one) whenever I have some...
configuration,nservicebus,publish-subscribe
Is the endpoint name the name of the MSMQ queue? Yes. Does that mean that every application has only one input queue for all message types? Yes. Each endpoint has a single queue associated with it, so all messages for that endpoint go through the same queue. Does adding...
javascript,events,promise,publish-subscribe
Alright, I have made my own solution similar to the one presented in the question. Welcome to the Promised Land...
javascript,mongodb,meteor,publish-subscribe,iron-router
You can do a simple join in the userPostAvatar publish function like this: Meteor.publish('userPostAvatar', function(postId) { check(postId, String); var post = Posts.findOne(postId); return Meteor.users.find(post.authorId, {fields: {profile: 1}}); }); This assumes posts have an authorId field - adjust as needed for your use case. Note three important things: You will need...
angularjs,ionic-framework,publish-subscribe,rootscope
I would need to see your ui-router config ($stateProvider) to further debug why your code isn't working as expected. It is most likely due to the homeTabCtrl not being instantiated at the time the $broadcast is called. One solution is to use a service. Make your changes to the service,...
javascript,mysql,node.js,sockets,publish-subscribe
Probably your easiest bet is to not listen for your mysql db being updated, but rather handle it as part of the pusher event handler. So when your pusher client receives an update, you would (at that point) both save to your mysql db as well as publish your own...
Setting resume_on_reconnect to false on the C side should prevent this behavior. If that doesn't work for you, and you're still having issues with this, shoot us an email at [email protected] and we're take care of you from there! geremy...
database,rest,time-series,publish-subscribe,iot
If you want a single solution, try ATSD, it does all of the above.
c#,msmq,nservicebus,publish-subscribe
Apparently, if the user account the service is running under doesn't have permission to access its own queues, that's not worth emitting anything into the logs. We have given the account permission to read from the queues and now it's operating correctly....
meteor,publish-subscribe,iron-router
Solution: Just add the following to your iron-router route() method. action : function () { if (this.ready()) { this.render(); } } Than the Template will rendered after all is loaded correctly....
activemq,message-queue,publish-subscribe,messagebroker
Use the ActiveMQ Failover transport and don't disable the inactivity monitor and the client will check the connection and automatically reconnect as needed. Without more information on you set-up that's about the best answer.
ruby-on-rails,rspec,redis,publish-subscribe
Create a mock for Redis and stub out the class and instance methods — new and publish, respectively. it "broadcasts creation" do redis = stub_redis Message.create(body: "foo") expect(redis).to have_received(:publish).twice end def stub_redis mock("redis").tap do |redis| redis.stubs(:publish) Redis.stubs(:new).returns(redis) end end ...
javascript,meteor,publish-subscribe
Meteor processes DDP messages (which include subscriptions) in a sequence. This ensures that you can perform some action like deleting an object and then inserting it back in the correct order, and not run into any errors. There is support for getting around this in Meteor.methods using this.unblock() to allow...
spring,spring-integration,publish-subscribe,mqtt
Your configuration looks good. However the MessageChannel is an abstraction for loosely-coupling and gets deal only with Message. So, you request a-la channel.send(Message<?>, topic) isn't correct for Messaging concepts. However we have a trick for you. From AbstractMqttMessageHandler: String topic = (String) message.getHeaders().get(MqttHeaders.TOPIC); ..... this.publish(topic == null ? this.defaultTopic :...
javascript,dom,publish-subscribe,event-delegation
Newer browsers Newer browsers support .matches: this.container.addEventListener('click', function(e){ if (e.target.matches('#game-again,#game-again *')) { e.stopPropagation(); self.publish('primo:evento'); } }); You can get the unprefixed version with var matches = document.body.matchesSelector || document.body.webkitMatchesSelector || document.body.mozMatchesSelector || document.body.msMatchesSelector || document.body.webkitMatchesSelector || document.body.matchesSelector And then use .apply for more browsers (Still IE9+). Older browsers...
javascript,jquery,model-view-controller,publish-subscribe
In your controller, you forgot to expose your events to the view (instead, you tie it to your pub/sub object). You should do something like : bindEvents: function() { $('body').on('click', '.js-data-request', this.request.bind(this)) } ...
mysql,node.js,redis,publish-subscribe
Redis is a advanced key-value cache and store.Its operations cannot be directly mapped to mysql. In redis you can set either key value pair or a hash under a key. That is : If you want to store your name in redis it can be done by: var client =...
events,promise,publish-subscribe
You'll want to have a look at (functional) reactive programming. The concept you are looking for is known as a Behavior or Signal in FRP. It models the change of a value over time, and can be inspected at any time (continuously holds a value, in contrast to a stream...
javascript,angularjs,design-patterns,publish-subscribe,mediator
Creating your own implementation of event emitter is counter-productive when writing an AngularJS application. Angular already provides all tools needed for event-based communication. Using $emit on $rootScope works nicely for global inter-service communication and doesn't really have any drawbacks. Using $broadcast on a natural scope (one that is bound to...
It doesn't work because you can only store EJSON-serializable objects in session variables. If you need the subscription handle outside of the current file, you'll need to store it in a global variable (perhaps under a namespace like Subscriptions - e.g. see richsilv's answer to this question.
Use the notify extender: app.viewModel.members.hasUpdate.extend({ notify: 'always' }); This will make sure hasUpdate's subscribers will always be notified, even if the new value did not change....
javascript,mongodb,meteor,publish-subscribe,meteor-blaze
Option 1: Keep track number of comment in the Posts collection itself. Each time new Comment inserted, update the counter: Posts.update( { _id: String }, { $inc: { commentsCount: 1 } } ) This way you doesn't need to subscribe Comments just to get the count, which will involve multiple...
c#,.net,redis,publish-subscribe,stackexchange.redis
The regular subscriber API should work fine - there is no assumption on use-cases, and this should work fine. However, I do kinda agree that this is inbuilt functionality that could perhaps benefit from helper methods on the API, and perhaps a different delegate signature - to encapsulate the syntax...
mongodb,meteor,publish-subscribe
"You can transform a collection on the server side like this:" http://stackoverflow.com/a/18344597/4023641 It worked for me. Unfortunately, changes in users collection will not update reactively these custom fields....
azure,publish-subscribe,azure-traffic-manager
No, this feature is used for Azure Web Apps (former Azure Web Sites), Cloud Services and Virtual Machines.
javascript,socket.io,sails.js,publish-subscribe
You better create different rooms for groups. CODE UNTESTED! Create a controller: NotificationsController.js module.exports = { subscribe: function(req, res) { // Get groupId of user by your method ..... ..... var roomName = 'group_' + groupId; sails.sockets.join(req.socket, roomName); res.json({ room: roomName }); } } Somewhere you can create notification: var...
So to answer my own question. The reason I was getting updates from every instance is simply because at the start of my application I triggered a findAll to get a list of available projects. As a result my socket got subscribed for all of them. The workaround would be...
c#,nservicebus,soa,publish-subscribe
No. This is called "Content-Based Routing", and it's not something that NServiceBus supports. Although NSB supports some broker-based transports (e.g. SQL Server, RabbitMQ), it is logically designed to be a distributed model. In order to do Content-Based routing, there needs to be a central hub that controls the delivery of...
Use Function.prototype.bind: PubSub.subscribe('topic', this.logger.bind(this)) ...
publish-subscribe,dds,data-distribution-service
The OMG standard for DDS (rev 1.2) does not supply an arbitrary limit to Topic name length. A Topic is identified by its name, which must be unique in the whole Domain. According to the RTI documentation (5.1.0 Users Guide pdf, Section 5.1.1, page 170), RTI's implementation of the Standard...
java,redis,publish-subscribe,jedis
After some research, I found that this is possible! The code stays the same, so long as you specify the CHANNEL_NAME in both to be the same (can maybe read from a properties file?) then there should be no problem. N.B. your subscriber has to be subscribed to the channel...
I found on this is because of the max objects per thread by default is set to 8 by the qos. To change this setting, before your first topic is created you must do the following. DomainParticipantFactoryQos factoryQos = new DomainParticipantFactoryQos(); DomainParticipantFactory.TheParticipantFactory.get_qos(factoryQos); factoryQos.resource_limits.max_objects_per_thread = 2048; DomainParticipantFactory.TheParticipantFactory.set_qos(factoryQos); This then sets the...
java,android,activemq,publish-subscribe
PubNub is as real-time as it gets... and it's super easy to make a Java server talk to Android device (in fact, PubNub has client SDKs for over 50 different platforms!). This same code will run on both Android and plain Java: import com.pubnub.api.*; import org.json.*; Pubnub pubnub = new...
javascript,node.js,publish-subscribe,eventemitter
You could use an EventEmitter for each channel. Also, you probably want to save references to callbacks, not to function name strings. var events = require('events'); var channels = {}; //publish data to a channel and emits all of the functions which are registered for listening to the channel function...
javascript,jquery,meteor,loading,publish-subscribe
The simplest solution is to activate the spinner in the event and deactivate it in the method call callback: 'click #methodButton' : function() { activateSpinner(); Meteor.call('method', function(ess, res) { if(err) throw err; deactivateSpinner(); }); } ...
azure,publish-subscribe,azureservicebus
Event Hubs have below advantage as compared with Azure ServiceBus: Its client-side cursor: Developers can use a client-side pointer, or offset, to retrieve messages from a specific point in the event stream Partitioned consumer support: Throughput Unit and inbound messages can be targeted at a specific partition through a user-defined...
javascript,knockout.js,single-page-application,publish-subscribe
The subscription's dispose method is what you're looking for. Knockout has no conception of "pages" or "navigation", so you'll have to handle this logic yourself. The simplest case looks something like: hasUpdateSubscription = app.viewModel.members.hasUpdate.subscribe(function () { viewModel.modificationCheck.update(); }); //When you change pages hasUpdateSubscription.dispose(); Realistically, though you probably want some more...
asynchronous,jms,publish-subscribe,tibco-ems,jms-topic
First thing first... I have questions regarding the scenario. Is this some kind of test/exercice, or are we talking about a real world scenario ? Are all client interested in the movie SEPARATE topic subscribers ? How does that scale ? I the plan to have a topic for every...
mongodb,meteor,aggregate,publish-subscribe,iron-router
Meteor does not support aggregation yet. You can get it to work this way though: Add in an aggregation package: meteor add meteorhacks:aggregate Use Meteor.call/Meteor.methods instead, since a aggregation result is static at this point. No reactivity supported. server side Meteor.methods({ "getTestList" : function() { return Tests.aggregate( [{ $project :...
methods,meteor,publish-subscribe
What is the difference between PubSub and Methods in Meteor?! Publications are reactive and they provide a cursor. Subscription gets you the matching publication on clientside in a minimongo database. On the other hand, methods must be called instead of subscribed and they are mainly designed to execute server...
publish-subscribe,mqtt,mosquitto
$SYS is being interpreted by you shell as an environment variable and is being substituted before mosquito_sub sees it. You can see this has happened by the topic string it reports in the SUBSCRIBE log statement. You should put quotes around the topic string: $ mosquitto_sub -d -t '$SYS/broker/clients/active' ...
feed,publish-subscribe,atom,pubsubhubbub
It should be at the feed level: http://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.3.html#discovery (that is btw. the same spec, Google is referencing).
java,unit-testing,publish-subscribe,dds
You can use lookup_topicdescription() on the DomainParticipant to get a reference to the previously created Topic, if it exists. In pseudo-code, you could do something like use lookup_topicdescription() to see if topic exists if topic does not exist use create_topic() to create the topic If your application does this in...
node.js,amazon-ec2,coffeescript,zeromq,publish-subscribe
The problem is I use a nodejs cluster module and in each of the work a zmq pub socket is created which binds on same port which messes up the issue. On my local machine its a single worker spawning.
playframework,websocket,publish-subscribe
def timeFeed = WebSocket.using[String] { implicit request => val in = Iteratee.ignore[String] val out = Enumerator.GenerateM( Future { getTimeAndLog }) (in, out) } calling GenerateM instead of repeat will have the desired results...
https://docs.meteor.com/#/full/meteor_subscribe Quoting the docs : Meteor.subscribe returns a subscription handle, which is an object with the following methods: stop() Cancel the subscription. This will typically result in the server directing the client to remove the subscription's data from the client's cache. So basically what you need to do is storing...
java,xmpp,publish-subscribe,smack
I was setting the JID of the payload item to the User's JID. As a result, I was overwriting the previous ID's and the previous submissions from the user was being overwritten. I set the PayLoadItem's ItemID to null and that let the server generate a unique ID each time,...
You should create different topics where different sets of subscribers are registered. Hazelcast does not have any filter techniques on those subscribers.
javascript,mongodb,meteor,publish-subscribe,iron-router
Your publish is publishing comments without any postId filter. Your helper, filters by postId. Maybe the 4 comments that get published are the ones that do not belong to the current post that is open? Could you try updating, your subscription to Meteor.subscribe('comments', { postId: this.params._id }, { limit: Number(Session.get('commentLimit'))...
python,sockets,proxy,zeromq,publish-subscribe
I found the solution for this problem, and even though I read the docs front to back and back to front, I had not seen it. The key is XPUB_VERBOSE. Add this line to after the backend initialisation and everything works fine backend.setsockopt(zmq.XPUB_VERBOSE, True) Here's an extract from the official...
mysql,node.js,redis,publish-subscribe
Could you not just add an updated column to your tables? You could add ON UPDATE CURRENT_TIMESTAMP on the column, which would automatically store the current time every time that row was updated. The rule is applied to the database itself, so you don't need to update any other clients...
meteor,publish-subscribe,minimongo
You probably do need to flush this data on logout, which will involve saving the subscription handle and then stopping it: // when you subscribe var reportHandle = Meteor.subscribe('companyReport'); // then when you want to log out reportHandle.stop(); Meteor.logout(); UPDATE If I understand your question, you want to make sure...
I have resolved this problem using the below code private void Poll() { while (Enabled) { try { BasicDeliverEventArgs objBasicDeliverEventArgs; //Get next message var boolMessageRecieved = _subscription.Next(60000, out objBasicDeliverEventArgs); //Deserialize message if (boolMessageRecieved) { var objEvent = DeSerialize(objBasicDeliverEventArgs.Body); if (objEvent != null) { registerService.Process(objEvent); _subscription.Ack(); } } else { //DB...
ruby-on-rails,websocket,publish-subscribe,faye
I will create a counter cache so when a new comment is posted the cache changes. I will render the model with the cache using: = sync partial: 'discussion', resource: discussion Then, when a comment is created, edited, deleted, partial should update. This will be the partial: li ul -...