Hi Magnus,
 

> One word: Middleware. 
>

sorry, I didn't found the old discussions here regarding rewind (maybe a 
typo in my search phrase). Is there any proposal planned to change the 
specs to allow a more effective input implementation? 

My first thought was something like an unrewindable_input() function, that 
provides an input stream that doesn't provide a rewind() interface, but 
buffers the data read through this interface, so that the original input 
can still provide this data. If all middleware would be aware of this 
interface and the final application wouldn't need to rewind(), the input 
would just have to store the part of the input that have to be processed 
twice.

Cheers,
Torsten 

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.