> I know I can use select() to check if the file descriptor is ready for a > write(), but that would still not be a way to determine if the file > descriptor is ready for the size of my particular write() and ensure that my > write() will return in a timely fashion ... it seems like it would still > leave me open for potential trouble or potential unwanted time delays. > I'm no expert and can't answer all your questions or give best design advice...but. If your using non blocking IO and select signals a write is available, then that write should always return in a timely fashion. Like you said there though, select won't tell you how much can be written, nor does the write call guarantee it will write everything you give it. As usual when doing non-blocking asynchronous type stuff, it will be up to you to do the book keeping and send any remaining data in subsequent writes. Though I seem to recall there may be some ioctl calls available that actually tell you how much data is ready for reading or writing on a file descriptor, but can't recall off hand...may well be platform/os/arch specific.
cheers ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
