Pound will process the entire response *header* in memory before sending it to the client. (So, HTTP response line and related headers) This is so pound can rewrite Location headers and verify a valid response from the server, as well as get important information like Content-Length, whether it's chunked or not, etc.
Once the headers complete, it will do direct stream copies from the backend to the client stream in 4k chunks. Joe > -----Original Message----- > From: Ariel [mailto:[email protected]] > Sent: Tuesday, November 16, 2010 9:28 PM > To: [email protected] > Subject: [Pound Mailing List] Does pound buffer data, i.e. can it spoon > feed clients? > > > I can't tell from the documentation, does pound buffer data from the > backend, storing it in memory (and releasing the connection to the > backend) then spoon feeding it to the client? > > If it does buffer, where does it store it, just in memory? Is there a > limit? > > Same question for uploads, does it buffer the entire upload first then > send it to the backend? > > -Ariel > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
