sockets and pipes.... 5194

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160

Dondo

Sounds like your master process will have at least two threads: one for prioritizing and performing your reads and writes to your devices, and one for communicating with the children and queuing requests for the r-w thread. Perhaps one r-w thread and message queue for each device (one for bus, one for each serial port) would be better.

If you want to cache values and your master process is mulbreasthreaded, you will have to have a synchronized data structure to put those values in. The question is whether any additional synchronization issues from giving children access to the structure will be more or less complicated than managing pipes-sockets.

Yeah, the semantics should be the same. You can either have one thread-process for each connection, or use the ONONBLOCK flag to deal with blocking. One thread per connection should introduce the same synchronization issues as a shared data structure, so nonblocking I-O would probably be the way to go over sockets.

You might also consider a watchdog process to handle bane errors, or maybe that's sort of what the timeout threads you mentioned earlier do.

- -- Neil T. Dantam Student, Purdue University -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU-Linux)

iD8DBQFDUoAWkZoFyDoa1YARA84yAJ9+wP75vvoTmuhF1TahS4hH909bFACeMkPe Y6q2AKD2TrzwoC1yP7wYjco= =7p3L -----END PGP SIGNATURE-----