News for hackers. Stuff that matters.
Re:Why Node.js streams are awesome by robfig on Sunday March 25, 2012 @10:34AM (#3752690)
Using the Play! Framework (Java):

  public static void myEndpoint() {
    HttpResponse resp = WS.url("url-of-file").get();
    InputStream is = resp.getStream();
    renderBinary(is);
  }
Or am I missing something?

(EDIT: This doesn't do the zipping or multiple files -- I guess I need a ZipOutputStream to take it the rest of the way)

Re:Why Node.js streams are awesome by arthurschreiber on Sunday March 25, 2012 @10:47AM (#3752715)
I don't know the Play! framework, but the main difference probably is the use of nonblocking IO in nodejs, in contrast to blocking IO in the example you just have given. (I'm not saying either is better).
Re:Why Node.js streams are awesome by simonw on Sunday March 25, 2012 @03:48PM (#3753588)
Will that definitely stream from one to the other without buffering the full file in memory? That's the main benefit of the Node.js streaming approach - it doesn't need to hold the whole thing in memory at any time, it just has to use a few KBs of RAM as a buffer.
Re:Why Node.js streams are awesome by robfig on Wednesday March 28, 2012 @10:46AM (#3766472)
Play! uses Apache HttpClient under the covers. I haven't tried it experimentally, but the documentation explicitly says that it's streaming.