29 Jan
2004
29 Jan
'04
7:52 a.m.
(Sean Kelly <sean@ffwd.cx>) wrote:
What remains an issue in my mind is how far to take this. Socket and file classes for each platform at least... what else?
TTY, USB, FireWire, Parallel, .....? Since file classes normaly also imply all other types of communication resources this should be enough I think. But then different methods of opening and parametizing need to be abstracted as well. Perhaps by an ioctl method or similar? Or what about a library/framework where the user optionally can plug in the system dependent low level part while providing some implementation for the usual resources. This could be done like the filebuffer concept in streams? Roland