STATUS
There was a bit more work to do with respect to XDR.
The XDR specification (RFC 1014 is the document I'm using) defines not only a wire protocol, but a notational convention used to describe complex types. As I was writing the sunrpc class, it occurred to me that I was needlessly limiting what it could do by building in call sequences to read and write XDR entities. Furthermore, XDR entities can contain other XDR entities and this self-referential schema couldn't be handled by my own implementation.
Therefore, I decided to pile a couple more layers on top of the XDR primitive class. Today's goal is to finish & test XdrEntity, a class responsible for parsing XDR entity specifications & translating them into primitive read and write calls.
The top class will be a light wrapper that manipulates the lower-level APIs.
The current sunrpc work is simplified by this decision. I didn't really waste any time, just decided to rearrange things a little.
In the end, I don't think I'll get to talking to instruments today. I can spend another four hours or so on this, then I have to switch back to real work. Sunday needs real work done too.
So, talking to instruments will have to wait until next weekend.
-SHAWN-
There was a bit more work to do with respect to XDR.
The XDR specification (RFC 1014 is the document I'm using) defines not only a wire protocol, but a notational convention used to describe complex types. As I was writing the sunrpc class, it occurred to me that I was needlessly limiting what it could do by building in call sequences to read and write XDR entities. Furthermore, XDR entities can contain other XDR entities and this self-referential schema couldn't be handled by my own implementation.
Therefore, I decided to pile a couple more layers on top of the XDR primitive class. Today's goal is to finish & test XdrEntity, a class responsible for parsing XDR entity specifications & translating them into primitive read and write calls.
The top class will be a light wrapper that manipulates the lower-level APIs.
The current sunrpc work is simplified by this decision. I didn't really waste any time, just decided to rearrange things a little.
In the end, I don't think I'll get to talking to instruments today. I can spend another four hours or so on this, then I have to switch back to real work. Sunday needs real work done too.
So, talking to instruments will have to wait until next weekend.
-SHAWN-
I heard from Brian, and he said the board of the LXI Consortium does in fact want to keep their discovery code for members only.
That's ok - as I mentioned I now have a complete picture of how to do it, so all I need is free time. I don't know when that will be but if the VPN keeps bouncing today I might have developments later (don't hold your breath)...
-SHAWN-
---
You are currently subscribed to vrf as: hua_jing@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".