Can be accessed using SCWorker.exchange property.
The exchange object is a top-level scBroker client which lets you publish events and manipulate data within your brokers - It represents a cluster of 1 or more brokers. You can use any method of an scBroker client on instances of this object (see scBroker Client). Note that the hashing function used by the SCExchange object to shard actions/channels accross brokers can be found in the sc-hasher module - You can use this function in your code to help with sharding (advanced use case). See this comment for details.
|'subscribe'||When the subscription succeeds.|
|'subscribeFail'||Happens when the subscription fails. The first argument passed to the handler will be the error which caused the subscription to fail.|
|'unsubscribe'||When the exchange becomes unsubscribed from a channel.|
If you're running the full version of SC (not just the standalone socketcluster-server),
|publish(channel, data, [callback])||Publish any JSON-compatible object/array or primitive to channel. Optional callback is in form callback(err) - Where err is undefined on success.|
|subscribe(channelName)||Subscribe this scBroker exchange client to the specified channel. This function returns a Channel object which lets you watch for incoming data on that channel.|
|unsubscribe(channelName, [callback])||Unsubscribe this scBroker exchange client from the specified channel. You can reactivate the Channel object by calling subscribe(channelName) again at a later time.|
|channel(channelName)||Returns a Channel instance. This is different from subscribe() in that it will not try to subscribe to that channel. The returned channel will be inactive initially. You can call channel.subscribe() later to activate that channel when required.|
|watch(channel, handler)||Capture data that is published on a particular channel. The handler function must be in the form: handler(data)|
|unwatch(channel, [handler])||Stop capturing data from channel. The handler function is options. If none is specified, it will remove all handlers from that channel.|
|watchers(channel)||Returns an array of all handler functions which are bound to channel.|
|destroyChannel(channelName)||Destroys the specified SCChannel object - This makes it unusable and will allow it to be garbage collected.|
|subscriptions(includePending)||Returns an array of active channel subscriptions which this exchange client is bound to. If includePending is true, pending subscriptions will also be included in the list.|
|isSubscribed(channelName, [includePending])||Check if exchange client is subscribed to channelName. If includePending is true, pending subscriptions will also be included in the list.|
|run(queryFn,[data,] callback)||This method is a wrapper around the scBroker run method. The queryFn function will be executed directly on one of your brokers and the result will be passed back to your callback. If your SC instance has more than one broker, the queryFn will be executed on the first one by default - In order to spread the load evenly between all your brokers, you should add a mapIndex key to your queryFn before you pass it to the run method. For example, if you wanted to map to a specific broker based on a string stored in channelName you would just go: queryFn.mapIndex = channelName; then you just pass it to exchange.run(queryFn, ...) as normal.|
|setMapper(mapper)||Allows you to define a mapping function which is used to map specific broker actions to specific broker processes in order to distribute the load between them (assuming you have more than 1 broker). This mapping function is particularly important for the subscribe and publish actions as it decides which brokers will handle what channel names. This is only for advanced use cases.|
|getMapper()||Returns the current mapping function which is used to map specific broker actions to specific broker processes. For the publish and subscribe actions, the default mapping function will shard channels such that each broker will handle approximately (1/n)th of all channels (where n is the number of brokers). This is only for advanced use cases.|
|send(data, mapIndex, callback)||
Send data to one or more brokers. mapIndex can be a number, a string, an array of strings or null.
If mapIndex is a number, it will cause the message to be sent to the broker with that id.
If mapIndex is a string, it will be hashed to a number and the message will be sent to the relevant broker.
If mapIndex is an array (of strings or numbers), the message will be sent to multiple brokers.
If mapIndex is null, the message will be sent to all brokers.
You can listen for the data on the broker (in broker.js) using
Because the exchange object potentially handles a cluster of local brokers, you can optionally use the setMapper(mapperFn) method to set a function which will be used to map individual scBroker actions to one of your brokers (assuming you have more than one). Changing the default mapper is an advanced use case though and you generally don't need to do it. The mapperFn takes three arguments:
|key||The key/keyChain (typically string or Array) which is was passed to this scBroker client method/action. If the method is 'query' then the key will be an scBroker query function which you will have to interpret in order to come up with a mapping.|
|method||The scBroker method which was invoked and needs to be mapped to one or more broker processes.|
|clientIds||An array of available scBroker client IDs which you can map to.|
The mapper must return either an ID (integer) or an array of IDs and SC will send the action to all corresponding brokers. So if the mapperFn returns 0, then the action wil be sent to scBroker broker with ID 0. If you return the clientIds array directly, then all clients will receive the action.