Current version: 0.4
This is a personal project, a side project, but one that I hope takes the same arc from my machine through the community and into vi.lib proper that the Actor Framework has done. Having said that, this is completely a side venture for now.
LabVIEW needs a better mechanism for converting objects to and from strings. This need includes both binary formats and human readable formats like XML. Improving object serialization has been planned since LVOOP’s inception, but never implemented. Many people think of the Flatten and Unflatten primitives as covering this task – particularly the binary format. The problem is that those primitives are only appropriate for intra-LabVIEW serialization. In other words, as long as LabVIEW is both the reader and the writer of the data, those primitives work well, but not so well when you must communicate with the outside world. Even within LabVIEW there are support gaps created by complex refactorings and client and server code that revs at different intervals.
The attached document has been through multiple revisions already. It is refined enough that I think a wider audience can comment on it meaningfully -- when an idea is poorly formed, the raw brainstorm just spins, and when it is too finalized, there's too much resistance to changes. At this point,I think it has enough meat to be reasonably chewed on.
Please let me know what you think. No deadline, but know that I am inching forward on this design and at some point, I'll start spinning code and see where it leads me.