The machine will generate hundreds, thousands, millions of Qson sqlite3 tables. Right now I rely on the knowledge of the clients, he knows what tables he gets and puts. Then files everywhere, this thing reads Json like CSV on steroids, with variable length rows ad ad hoc naming. So Json has placed CSV.
I get stuck as the software geek. Every Json that enters the system has to be named inthe local table index space. That would be sqlite_master, I presume.
Naming spaces are web wide, though often sparse for some applications. They are indices, and for a table, they have to include and ip or url. So an entry into a server, will cause a migration out of updates. So every reference to a table is bound with it potentially web wide presence, it has to be specific. Hmm... can this wait until we get the machine out, then folks will play around with the problem. Yes, set this up for beta, for alpha its local tables only, and client knowledge of where things are. Right now I routinely load Json word lists, I should upload one of these for testing. They are variable length groups of words.
What the client sees:
The client bookmark, for example, he may think they are local. But in the extended pakage, the provider can extend his bookmarks closer to data. Or the client can drag his book marks to the local server they travel. Bookmarks are web tags, literally, they are table you own somewhere on some server sqlite platform. It is like controlling names Json space in the web, and you have developer provided tool to fill this indexed space with goodies.
Anyway, naming is infringing on those right assigned to others, once again.
No comments:
Post a Comment