I need to work stuff out that requires Json, like feed configuration objects to the machine. I don't want to make my Lazy Json console look stupid, yet I need a smooth way to direct steams to the machine internals. The solution is do something that is the least weird looking.
OK, problem solved, an I am working on it.
Stretching my simple brain as we speak. So many issues, industry so far behind, few clues. The problem is that the engine needs to be transparent, as if it is not even there. The machine only knows about a single triple, the exception being a block of triples for configuration. The disposition of a table is at that application layer, the overloads. So the the middle ware layer, the layer that knows about he various overloads on link, that layer has to determine the disposition of a new table (graph). If the graph is a configuration graph, then just let the machines handlers have it.
The problem is compounded a bt because the handler wants to decide where the data goes and process it without having the machine reset the sqlite3 statement.
Still fiddling with the code, no inspirations are striking me.
Finally, a solution that would make any geek say, hell that makes sense. If a bson stream is dedicated to installation and configuration, then so be it, te machine will configure itself on the fly,
No comments:
Post a Comment