Ben Newman f5821c88ee Allow server-side method implementations to return a Promise. ...

This does not mean that Meteor.call or Meteor.apply now return a Promise.
Completion of the method call is merely delayed until the Promise is
resolved or rejected, at which point the calling code asynchronously
receives the resulting value or exception.

These changes were inspired by this forum thread:
https://forums.meteor.com/t/fibers-and-meteor-promise-npm-pacakge/6531/7

2015-08-17 14:05:21 -04:00

..

.npm/package

ddp-server does not use faye-websocket directly

2015-04-14 21:34:46 -07:00

crossbar_tests.js

Resolves: ddp package should be split in two

2015-04-14 21:34:46 -07:00

crossbar.js

Extract MongoId into a separate package to reduce the dependencies on minimongo

2015-06-12 11:07:20 -07:00

livedata_server_tests.js

Allow server-side method implementations to return a Promise.

2015-08-17 14:05:21 -04:00

livedata_server.js

Allow server-side method implementations to return a Promise.

2015-08-17 14:05:21 -04:00

package.js

Allow server-side method implementations to return a Promise.

2015-08-17 14:05:21 -04:00

server_convenience.js

webapp and routepolicy need no longer be weak deps

2015-04-14 21:34:46 -07:00

session_view_tests.js

Resolves: ddp package should be split in two

2015-04-14 21:34:46 -07:00

stream_server.js

webapp and routepolicy need no longer be weak deps

2015-04-14 21:34:46 -07:00

writefence.js

Catch up to oplog at most once per write fence

2015-07-09 09:25:56 -07:00