It would be really awesome if datastores exposed meta-data about themselves in some standardized way in the datastore itself. This way, you don't need a reference to the datastore object to interrogate its properties; so that remote datastores can ask metadata questions. Possible use-cases:
Check the number of subscriptions on an endpoint from within the datastore (Ooooo, maybe even subscribe to change event, so that you are informed when the number of subscriptions changes?!)
Ask about the path tree structure without actually get the data
Register documentation about what data in endpoints are, so that remote stores can see the docstrings before interacting with the endpoint's data (would be very helpful if a .call functionality get's introduced: https://github.com/Daxbot/entangld/issues/21)
My proposal is to have endpoints change from being simple objects to instances of a new EntangldNode, which has standard metadata associated with it, then we either include a new operation like .interrogate or .query which can query that metadata on a node.
It would be really awesome if datastores exposed meta-data about themselves in some standardized way in the datastore itself. This way, you don't need a reference to the datastore object to interrogate its properties; so that remote datastores can ask metadata questions. Possible use-cases:
.callfunctionality get's introduced: https://github.com/Daxbot/entangld/issues/21)My proposal is to have endpoints change from being simple objects to instances of a new EntangldNode, which has standard metadata associated with it, then we either include a new operation like
.interrogateor.querywhich can query that metadata on a node.