>>>>> "LT" == Leopold Toetsch <[EMAIL PROTECTED]> writes:
LT> Uri Guttman <[EMAIL PROTECTED]> wrote: >> this is another reason to drop seek/tell as separate ops and just add a >> seek offset as an arg to the i/o ops. tell is useless in the aio >> world. the user code needs to manage its own seek location and pass it >> into each call. LT> Well, yes that's true. OTOH we might want to support "traditional" IO LT> sequence of operations. The aio read and write calls have the file LT> positions as argument, sync read and writes don't have it. It could be LT> useful to support both flavors e.g. for libraries that are called from LT> different HLLs. i am not against having a sync api but as dan said it should be a wrapper around the async stuff. but as we agree (and dan hasn't acked yet) the aio ops need a seek arg and the seek/tell ops should be dropped LT> A (synced) lseek(2) can only return, if all async operations are LT> completed. The real problems jump in, when code is mixing LT> sync/async IO. but a synced lseek with async ops out there is just what you say are real problems. coder emptor when doing that. seek should pretty much be seek as it is now. it has nothing to do with aio and is a non-blocking op in my book. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
