Skip to content

Instantly share code, notes, and snippets.



Last active Mar 18, 2016
What would you like to do?
Meteor Latency Compensation - The Correct Way

##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)

//located in: client/methods/posts.js
"post": function(postData) {
postData.submitted =;
//located in: server/methods/posts.js
"post": function(postData) {
var user = Meteor.user();
if(!postData.url || !postData.title) {
throw new Meteor.Error(422, "URL and Title must exists!");
if(!user) {
throw new Meteor.Error(401, "Unauthorized!");
var existingPostWithUrl = Posts.findOne({url: postData.url});
if(existingPostWithUrl) {
throw new Meteor.Error(302, "URL already exists", existingPostWithUrl._id);
var post = _.extend(_.pick(postData, 'url', 'title', 'message'), {
author: user.username,
userId: user._id,
//apply some secret formula here
var Future = Npm.require('fibers/future');
var future = new Future();
//for just show the latency
Meteor.setTimeout(function() {
post.title += " - server";
}, 5000);
var postId = Posts.insert(post);
return postId;

This comment has been minimized.

Copy link

@fpoirier1 fpoirier1 commented May 1, 2014

There is a typo at line 34 of server-method.js it must be future.return(). Thanks for the clarification though !


This comment has been minimized.

Copy link

@yauh yauh commented May 21, 2014

Wouldn't it make sense to somehow extend the client method on the server, much like inheritance in object orientation? The shared part of the post method wouldn't need any copy/pasting then.
Something like

Method post-server extends method server

Any downsides for that?


This comment has been minimized.

Copy link

@seeekr seeekr commented Jul 1, 2015

This gist still pops up when searching for Meteor latency compensation. But I think this is mostly or completely obsolete. ping @arunoda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment