// @todo how does "exclusive" play into the controllers, does "exclusive" mean only one provider can exist for a given protocol and realm? what does non exclusive mean?
ks_hash_t*protocols;// protocols that have been published with blade.publish, and the details to locate a protocol provider with blade.locate
ks_hash_t*protocols_cleanup;// keyed by the nodeid, each value is a hash_t* of which contains string keys matching the "protocol@realm" keys to remove each nodeid from as a provider during cleanup
ks_hash_t*protocols;// protocols that have been published with blade.publish, and the details to locate a protocol controller with blade.locate
// @todo build up json-based method schema for each protocolrpc registered above, and pass into blade_handle_rpcpublish() to attach to the request, to be stored in the blade_protocol_t tracked by the master node
// @todo to properly maintain protocol details tied to a specific node like this participants list requires a way to know if a specific node of interest goes offline to cleanup associated details
@@ -314,19 +340,24 @@ int main(int argc, char **argv)
blade_identity_destroy(&target);
if(connected){
cJSON*channels=NULL;
// @todo use session state change callback to know when the session is ready and the realm(s) available from blade.connect, this hack temporarily ensures it's ready before trying to publish upstream