Meteor#unsetCallback is now Meteor#removeCallback or Meteor#removeCallbacks.
You now have to establish the connection to the server manually. Before, this was done automatically in the Meteor constructor. To update your code, call Meteor#connect somewhere after calling the Meteor constructor. It is recommended to place the call after registering the callback via Meteor#addCallback.
You now have to unregister all callbacks manually by calling either Meteor#removeCallback or Meteor#removeCallbacks. Before, this was done automatically when disconnecting. It is recommended to remove the callback(s) just after calling Meteor#disconnect, whenever you do that.
Exceptions triggered while connecting and disconnecting are now correctly delivered in MeteorCallback#onException.
ocram
commented
8 years ago
Preliminary notes:
Meteor#setCallbackis nowMeteor#addCallback.Meteor#unsetCallbackis nowMeteor#removeCallbackorMeteor#removeCallbacks.Meteorconstructor. To update your code, callMeteor#connectsomewhere after calling theMeteorconstructor. It is recommended to place the call after registering the callback viaMeteor#addCallback.Meteor#removeCallbackorMeteor#removeCallbacks. Before, this was done automatically when disconnecting. It is recommended to remove the callback(s) just after callingMeteor#disconnect, whenever you do that.MeteorCallback#onException.