Server2server

[neurobe]

Adds server-server topology
by adding a second global 'SvrStreamer',
allowing normally client-side code to run in server.

Note that Tracker.nonreactive is continued to be used (and works ok), however it is documented for client-side use only.

RocketChat:meteor-streamer client - server code unchanged.

[rodrigok]

@neurobe Can you explain exactly what are you trying to do?

[neurobe]

this PR allows one meteor server to act as a client to another meteor server. This allows for
server <> client
server <> remote client ( a previous PR)
server <> remote server (this PR)
And yes it works OK.
Why?
There are many applications where there is a front end meteor application and a back-end meteor application.

In my particular use case I have a meteor server interfacing to a USB port to talk to a instrument. The local server then sends the data to a network server. This runs just fine at 1000 samples per second!

[neurobe]

BTW,
I use your very nice streamer 'allow' implementation to allow a network side client to select between multiple instruments. Excellent! Thank you. 'allowRead' is efficient and can handle the 1000 smples per second required.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}