_publishCursor handle

[ccorcos]

I'm looking at the code under the "Advanced Publications" section, specifically the stuff with Mongo.Collection._publishCursor.

It seems that Mongo.Collection._publishCursor will always return undefined rather than a handle that can be stopped...

[ccorcos]

if I go into the meteor shell and run console.log(Mongo.Collection._publishCursor.toString()), I get this:

I20150506-17:48:49.658(-7)? function (cursor, sub, collection) {                                                // 302
I20150506-17:48:49.658(-7)?   var observeHandle = cursor.observeChanges({                                                                         // 303
I20150506-17:48:49.658(-7)?     added: function (id, fields) {                                                                                    // 304
I20150506-17:48:49.658(-7)?       sub.added(collection, id, fields);                                                                              // 305
I20150506-17:48:49.658(-7)?     },                                                                                                                // 306
I20150506-17:48:49.658(-7)?     changed: function (id, fields) {                                                                                  // 307
I20150506-17:48:49.659(-7)?       sub.changed(collection, id, fields);                                                                            // 308
I20150506-17:48:49.659(-7)?     },                                                                                                                // 309
I20150506-17:48:49.659(-7)?     removed: function (id) {                                                                                          // 310
I20150506-17:48:49.659(-7)?       sub.removed(collection, id);                                                                                    // 311
I20150506-17:48:49.659(-7)?     }                                                                                                                 // 312
I20150506-17:48:49.659(-7)?   });                                                                                                                 // 313
I20150506-17:48:49.659(-7)?                                                                                                                       // 314
I20150506-17:48:49.659(-7)?   // We don't call sub.ready() here: it gets called in livedata_server, after                                         // 315
I20150506-17:48:49.660(-7)?   // possibly calling _publishCursor on multiple returned cursors.                                                    // 316
I20150506-17:48:49.660(-7)?                                                                                                                       // 317
I20150506-17:48:49.660(-7)?   // register stop callback (expects lambda w/ no args).                                                              // 318
I20150506-17:48:49.660(-7)?   sub.onStop(function () {observeHandle.stop();});                                                                    // 319
I20150506-17:48:49.660(-7)? }

So it appears, it does the stopping for you and doesnt return the handle. So the code could use an update.