Kevin, In regard to asynchronous I/O, you said: > This applies equally to the request model. Nothing prevents the submission > (but not necessarily resolution) of a later I/O request during resolution > of an earlier request if those requests are independent (and the request > stream is hyper-strict). to which I replied: | Isn't the resolution of an I/O request essential? If we cannot get the | result of an I/O request out of the response stream, does that not indicate | that the stream model is inadequate for allowing the kind of parallelism I | mentioned? Nigel asked me what I was getting at here, so I suppose other people are wondering too. I would suggest that parallelism is a red herring (with regard to streams vs. continuations). The real issue is polymorphism. (In my reply above I was thinking of polymorphic, asynchronous I/O requests). A stream model (in a statically typed language at least) will never be able to guarantee type safety when extracting the result of a polymorphic request. Thus I suggest that we do away with the stream model altogether. Kevin, why should the request stream be hyper-strict? _______________________________________________________________________________ [EMAIL PROTECTED] Evan Ireland, Department of Computer Science, +64-6-3569099 x8541 Massey University, Palmerston North, New Zealand.
