GDP

To demonstrate GDP as a middle-ware and leverage the benefits of accessors, it is imperative that GDP accessors work neatly. The GDP accessor interface is currently split into a number of accessors (subscription, reads, writes, etc). Based on a meeting with Christopher last week, here is a summary (and current status) of desired accessor hosts:

• Ptolemy: Currently works via a translation of GDP C API to Java and then executing JavaScript via Nashorn. It mostly works, but has some superficial usability issues. My understanding is that the translation of API calls works well, however the mapping of accessor functionality to the translated API calls needs a revisiting. Some documentation updates wouldn't hurt much.
• Node.js: Mostly works using FFI, but has some issues with cross platform (see #102).
• Web-browser (or similarly minimal platform, such as a sign-post): currently, the plan is to use the REST interface (see #95). It currently works, but needs a good way to handle subscription (see #108).