a little of housekeeping
Desired services api would look like this.
Note streaming storage features.
added optimist dependency
That's how it looks now:
We pretend to have streaming read from storage.
We resolve service methods dynamically.
Async resolution with callbacks would be dreadful, so some kind of
promise/future machinery is used.
Need for synchronous resolution yet has to be discussed.
despite we have service method table from Locator and parse incoming
cocaine messages at binding level, we need this to send any outgoing messages
base class for any service interaction
duplex stream that represents either one service method call either
worker method invocation
Worker class. That's it.
some useful stuff
services machinery
logger and storage services definitions
missing index.js
fix the miss
add missing requires
properly pass endpoint parameters to low-level channel
other minor fixes
use global per-service session counter
minor fixes:
* actually resume session
* actually emit end when choke received
* actually send message id
resolve circular dependency Service->Locator->Service
also, actually use Locator instance to resolve services
few minor fixes