file io

- We still need to come up with a naming metaphor for this!
- it is a pipeline communication to stream a file from a server to a client.
- It follows a model similar to: http://zguide.zeromq.org/c:fileio3
If I understand this correctly:  The reason why this crash doesn't crash horribly when ```p``` goes out of scope is that zmq has "newed or malloced" and copied the memory internally. Which means the sending of stack variables in ```SendThreadSendThirtyDie``` is fine since the delete is the responsibility of the Sender.   Is this correct?

    If this why you use ```free```, since zmq uses malloc internally?