We've spent a lot of time looking at how a server-side publish function sends added, changed and removed messages for a collection. But what happens to those messages on the client? How does Meteor connect those messages to a browser database cache like MiniMongo? It uses something called a Store. In this video we'll create our own store so you can see the minimum interface between MiniMongo and a Livedata connection.
One-On-One Questions or Comments?
Something not making sense, want to share your thoughts or just say hello? I check this daily!