You may be asking the wrong question. Devices have a specific function - be it storage, redirection, hardware interfacing, whatever - and your notional device would do nothing more than hold the data for a while and return it. If that's the case, then why not just use a named pipe? You could write to it and read from it at your leisure, and all you need to know is what already know (at least I assume you do) about reading from/writing to filehandles.
In reply to Re: device I/O interceptor
by oko1
in thread device I/O interceptor
by tom93
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |