##Meteor Latency Compensation - The Correct Way
This is a kind of correction I wan't make regards to the concept describe in discover-meteor book
For the latency compensation to occur we cloud simply share the same method in the client/server. We can do this by simply putting the method under a place which can see by bot the server and client.
But practically(not all the time) we should not do that. In the server code we might have some logic which should not share. Or simply we might have some secret tokens.
So the correcy approach is define the method (in this case
post) seperately in the two context. as shown below
In the client implementation just update the collection (and do the validations)