search for: appriopr

...y you wouldn't make it all based on files > > and not on streams :s It's just a major disavantage in my opinion > > an api cannot be all things to everyone. sure it can: you just have to make some different cases (low cpu power device/streaming or multi-core cpu) and call the apprioprate functions you keep making this > assertion but if you actually tried to implement it (and I hope > you will) the problems we are all bringing up will quickly become > obvious. > > your own lame-mt example is not an incremental improvement but a > significant rewrite of lame...

--- Harry Sack <tranzedude@gmail.com> wrote: > 2007/9/8, Josh Coalson <xflac@yahoo.com>: > > > > it actually is complicated. the libFLAC api is not suited to a > > multithreaded design because the i/o is stream-based, not file- > > based. flac(.exe) is the file-based wrapper around libFLAC that > > allows it to work on files. the way libFLAC buffers