Nate Lawson <[EMAIL PROTECTED]> writes: > May I humbly propose that the API is broken and should be reworked? My > frustration with cached_connection common/ftp sharing and this thrashing > trying to overload the return value are signs that the API needs > rethinking.
What do you mean "overload the return value"? _fetch_read(), _fetch_write() and _fetch_writev() are meant to return the same values in the same cases as read(2), write(2) and writev(2) would. The only difference should be in what value errno can have after they return (I don't think any of the system calls can set it to ETIMEDOUT). None of this has anything to do with cached connections, and I do not agree that caching should be done in common.c, because it relies on information (such as login and password) which is not and should not be available at that layer. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
