Up to this point, we have been using
autopublish. Meaning, we haven't had to code specific publish events for any events or collections. This is great for testing, but we want to have a bit more control over what events and documents get published, so we can improve both performance and security.
If we have a large dataset, we may not want to return the entire collection every time. If
autopublish is being used, the entire collection will return, and that can slow things down, or it can expose data we don't want to have exposed.
The time has come to turn off
autopublish. Temporarily stop your Meteor application (if it's still running) by opening the terminal window you ran the
meteor command from. You ...