tag:blogger.com,1999:blog-4222197394079314848.post3076565809915537551..comments2023-05-10T02:34:45.071-05:00Comments on Mark A. Ziesemer: Sun's version of "640k": 2GB ServletResponse Content-LengthMark A. Ziesemerhttp://www.blogger.com/profile/12752422620777325409noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4222197394079314848.post-74095734030462279572009-05-28T17:38:21.251-05:002009-05-28T17:38:21.251-05:00I too agree that it's a very disappointing respons...I too agree that it's a very disappointing response from the reviewer. Things have changed a lot in technology since that bug was posted and the response to it.<br />It's definitely high time Sun digs back into this and have this fixed.<br />I posted a comment on the bug on their site, and would ask my entire sea of Java developer friends to do the same.<br />Atleast that might cause Sun to Phaninoreply@blogger.comtag:blogger.com,1999:blog-4222197394079314848.post-88629408012808408092008-08-26T20:46:00.000-05:002008-08-26T20:46:00.000-05:00While exploring the possibility of a server implem...While exploring the possibility of a server implementation using HTTP 1.1 to stream large video content I was dismayed to find this had never been addressed. Especially since HTTP/1.1 range requests allow a client to request portions of a resource. It would seem the complete solution would be to provide a long content length and additional information (normalized via Java APIs) about the Anonymousnoreply@blogger.com