The Remoting 3 prototype has a generic streaming mechanism that's pretty similar to what you propose. Basically any object that is recognized as a stream type is replaced with a proxy that moves the data over the wire. This way you can create custom stream types beyond the predefined type, and a single request can contain multiple streams; data can be pushed from server to client (e.g. pass an OutputStream as part of the request), or pulled from client to server (e.g. pass an InputStream) The predefined stream types are defined here: http://anonsvn.jboss.org/repos/sandbox/david.lloyd/remoting3/api-proto/sr... Also, Reader/Writer and Input/OutputStreams will be supported by default. Please have a look over this material and let me know if there are any key features that are missing... specifically if you have any thoughts about things like flow control, or any insights based on your implementation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101746#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...