Saturday, November 3, 2018

Grouping cursors

One of those, not much work required when managing the cursors.  The cursors are trapped in their own dependency tree, their attachments will pause when waiting for another cursor to catch up.  If join is idle enough to be flipping though the linear stack, then the turn around time is short, round robin access work just like even polling.

I am trying to avoid work here, and let the stack resolve all iots joins naturally by keeping the cursors consistent within a join instance.  The executive need not be smart.  It mostly gathers state information on the data flow, attachments manage themselves otherwise.  So, the join protocol is mostly a consensus, not a technology. It is an agreement about which side, right or left, is mostly searching the other. An agreement to use compatible match functions.  Otherwise, join, all 30 lines of it, is just a step and fetch manager.  More of a human agreement, mostly about a few boundary conditions. Just want to add the skip function to csv files.

PutEnv and GetEnv both working, the macro symbol tables. I wrote them to file as plain text, line by line pairs.  You can edit the list in the editor, then load it back into join all you want, a great productivity tool.

Based on that, iwant to feed it search script via the command processor, using the Console attachment. The Console device opens to the keyboard, but I can direct it to macro processor, make life even simpler for searching. Keep a collection of search strings in g\the macro tables.

Where macros help

Setting up these intermediate memory flows, you want detai in defining maxim sizes, total wize and other constraints.  Setting up for file IO depends on the file and attachment. So the command back to configure are variable number of arguments among the attachments,  Macros solve this, especially going into the  editor and just carefully typing in the set up and go commands. The command set up can be used over ad  over again by different cursor groups. We get a number of environments, all in oncise editable files of plain text.

No comments: