Skip to content
This repository
Browse code

remove superflous discussion

  • Loading branch information...
commit a7a2342400d07d79c3c9956cecb55f0568ec2b7b 1 parent 2d70786
Tatsuhiko Miyagawa authored November 11, 2009

Showing 1 changed file with 0 additions and 12 deletions. Show diff stats Hide diff stats

  1. 12  PSGI/FAQ.pod
12  PSGI/FAQ.pod
Source Rendered
@@ -354,18 +354,6 @@ backends simple. Other options, like allowing an array ref
354 354
 in addition to a plain scalar, make either side of the code
355 355
 unnecessarily tedious.
356 356
 
357  
-Note that I'm talking about multiple header lines with the same key,
358  
-and NOT about multiple header values (e.g. C<Accept: text/html,
359  
-text/plain, *>). Joining the header values with C<, > is obviously
360  
-the application's job. L<HTTP::Headers> does exactly that when it's
361  
-passed an array reference as a header value, for instance.
362  
-
363  
-The other option is to always require the application to set a value as
364  
-an array ref, even if there is only one entry: this would make backend
365  
-code less tedious, but, for the exact reason of multiple header values
366  
-vs. multiple header lines with the same name mentioned in the paragraph
367  
-before, I think it's confusing.
368  
-
369 357
 =head3 No iterators support in $body?
370 358
 
371 359
 We learned that WSGI and Rack really enjoy the benefit of Python and

0 notes on commit a7a2342

Please sign in to comment.
Something went wrong with that request. Please try again.