--- AnyEvent-HTTP/HTTP.pm	2009/07/07 00:15:32	1.44
+++ AnyEvent-HTTP/HTTP.pm	2009/07/25 01:29:09	1.46
@@ -50,7 +50,7 @@
 
 use base Exporter::;
 
-our $VERSION = '1.4';
+our $VERSION = '1.41';
 
 our @EXPORT = qw(http_get http_post http_head http_request);
 
@@ -223,7 +223,10 @@
 be extracted, or when the body should be processed incrementally.
 
 It is usually preferred over doing your own body handling via
-C<want_body_handle>.
+C<want_body_handle>, but in case of streaming APIs, where HTTP is
+only used to create a connection, C<want_body_handle> is the better
+alternative, as it allows you to install your own event handler, reducing
+resource usage.
 
 =item want_body_handle => $enable
 
@@ -245,7 +248,7 @@
 push-style twitter API which starts a JSON/XML stream).
 
 If you think you need this, first have a look at C<on_body>, to see if
-that doesn'T solve your problem in a better way.
+that doesn't solve your problem in a better way.
 
 =back
 
@@ -311,8 +314,8 @@
    _slot_schedule $_[0];
 }
 
-our $qr_nl   = qr<\015?\012>;
-our $qr_nlnl = qr<\015?\012\015?\012>;
+our $qr_nl   = qr{\015?\012};
+our $qr_nlnl = qr{(?<![^\012])\015?\012};
 
 our $TLS_CTX_LOW  = { cache => 1, sslv2 => 1 };
 our $TLS_CTX_HIGH = { cache => 1, verify => 1, verify_peername => "https" };
@@ -490,7 +493,7 @@
 
                # headers, could be optimized a bit
                $state{handle}->unshift_read (line => $qr_nlnl, sub {
-                  for ("$_[1]\012") {
+                  for ("$_[1]") {
                      y/\015//d; # weed out any \015, as they show up in the weirdest of places.
 
                      # things seen, not parsed: