<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 17-May-08, at 1:36 PM, Avi Bryant wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Sat, May 17, 2008 at 9:48 AM, Colin Putney <<a href="mailto:cputney@wiresong.ca">cputney@wiresong.ca</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="Ih2E3d"><br></div> Heh - I've long had nearly the opposite question: Why was support for read-write streams ever needed? I can't recall *ever* using it in my own code, nor encountering it in anyone else's.</blockquote><div><br> </div><div>What about files?</div></div></blockquote><br></div><div>Good point. A lot of files are read-only or write-only, but not always. MC2's file repository both reads and writes on the same file stream. So I guess I have encountered it in someone else's code. :-)</div><div><br></div><div>Still, I do think separate streams for reading and writing to the same file would be fine as an API.</div><div><br></div><div>Colin</div><div><br></div></body></html>