Does your answer imply that the servlet getReader() method returns the content in chunked format? Ie. the servlet engine does not interpret or aggregate the chunks ? The servlet API is very unclear in this area, I just want to make sure that my thread reading the socket can read the exact number of content bytes and not block unnecesarily AND that this is standard across all servlet compliant engines.
Thanks for your help! Bill. -----Original Message----- From: Manty, George [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 14, 2003 09:30 AM To: Tomcat Users List Subject: RE: Receiving Transfer-coding: chunked To make things easier use something like the Jakarta commons projects FileUpload API in your servlet to parse the request: http://jakarta.apache.org/commons/fileupload/ Hope that helps, George -----Original Message----- From: William Bondy [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 14, 2003 9:16 AM To: '[EMAIL PROTECTED]' Subject: Receiving Transfer-coding: chunked If a client sends content (via a POST) using chunked transfer-coding, how is the content retreived via a servlet? Does the user need to be concerned with getting the inputstream and handling the content directly in chunked format since the length may not be known at processing time? I.e. the content-legnth may be set to -1... Bill. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
