corto
corto copied to clipboard
A hierarchical object store for connecting realtime machine data with web applications, historians & more
Currently in the select, the tree operator `//` will allow a user to select a subtree of an object recursively. A user can for example request all objects under `corto`...
The `corto_select` call can potentially return data from one or more replicators, which most likely will require accessing remote resources through databases, REST APIs, filesystems, messaging protocols etc. Retrieving these...
Since function calls in Corto can be executed on a remote node, having to do a blocking wait for a response (in order to mimic 'traditional' function behavior) could hurt...
Take the following inheritance line `TestJsonInt < TestJsonValue < BaseTestJson < Suite`. `TestJsonInt` has the method `testMaxInt16`, together with many other methods. The classes exist in a package with a...
Objects are being memory managed using reference counting. When an object reaches reference count zero it will be destructed. The current approach has however some issues. First and foremost cycles...
Based on a conversation between @Seldomberry/owners: Important factors to take into consideration: - What are the needs of the intended primary users of Hyve? - Can we define the permitted...
Generated methods for virtuals include snippets like the following: ``` /* Lookup method-object. */ _method = corto_interface_resolveMethodById(_abstract, _methodId); corto_assert(_method != NULL, "unresolved method '%s::visitScope(Scope node)@%d'", corto_idof(_this), _methodId); ``` `corto_idof(_this)` fails...