Meteor data flow data without persistence: setting the best / correct practice

I just want to monitor or handle interactions with "things" that send some data and listen for actions.

An example of sending pulses read or generated by the server to all connected and listening clients.

This data does not need to be stored in a Mongo collection, but is only available as a volatile dataset or object.

There are a few packages out there that do types like YookanOO / streamy , but I don't know if that is correct.

I created an example with a local collection of Meteor clients on meteorpad:

Sample_Publish_to_Local-Collection

Q: What's the correct solution? Local collections or a library like Yookan: Streamy ?

+3


source to share


1 answer


I would go with what you already do. Post / subscribe with this. Already /this.changed/this.added etc.



0


source







All Articles