Saturday, February 11, 2012

Doing the Bson uglies, what about Javascript

In the machine. Folks who follow the drama knew what happened a month or tow ago.I connected the main path in the machine and all my programmer kludges that I used for testing went away. These were hooks I put in the parser. I had a choice, leave a lab kludge, or jump in and process Bson uglies and do installs correctly from Bson. So I now have the ugly module wit limited local symbol indexing, just enough so I get symbols to use in install. The Ugly processor is where graph convolution takes place when the customers want to do joins on Bson.

On embedding Javascript.

There is no rush. Google has a nice Javascript processor that is easily embedded, but actually hat is likely to be accomplished by others, though I might get stuck with the job. After that, go whole hog and load up node,js if you want. However, with installs the thing is such a simple and complete Bson database that I am in no hurry. Netio for the thing is deliberately slim as I know that customers might want node.js. But nod.js is not for wandering Bson Bots, they like fast, binary ACID Bson transfers, and they are self directing via the ugly processor.

No comments: