ktats****@users*****
ktats****@users*****
2011年 4月 30日 (土) 13:41:38 JST
Index: docs/modules/Furl-0.24/lib/Furl/HTTP.pod
diff -u docs/modules/Furl-0.24/lib/Furl/HTTP.pod:1.4 docs/modules/Furl-0.24/lib/Furl/HTTP.pod:1.5
--- docs/modules/Furl-0.24/lib/Furl/HTTP.pod:1.4 Sat Apr 30 04:20:39 2011
+++ docs/modules/Furl-0.24/lib/Furl/HTTP.pod Sat Apr 30 13:41:38 2011
@@ -1,7 +1,5 @@
=encoding utf8
-=encoding utf8
-
=head1 åå‰
=begin original
@@ -410,7 +408,7 @@
=begin original
-(=item Why IO::Socket::SSL?)
+(Why IO::Socket::SSL?)
=end original
@@ -422,14 +420,14 @@
Net::SSL ã¯ãƒ‰ã‚ュメントãŒè²§å¼±ã§ã™ã€‚
+=item env_proxy ã¯ãªãœã‚ªãƒ—ショナルãªã®ã§ã™ã‹?
+
=begin original
-(=item Why is env_proxy optional?)
+(Why is env_proxy optional?)
=end original
-=item env_proxy ã¯ãªãœã‚ªãƒ—ショナルãªã®ã§ã™ã‹?
-
=begin original
Environment variables are highly dependent on each users' environment,
@@ -440,14 +438,14 @@
環境変数ã¯ãƒ¦ãƒ¼ã‚¶ãƒ¼ã®ç’°å¢ƒã«å¼·ãä¾å˜ã—ã¾ã™ã€‚
ã†ã¾ãå‹•ã‹ãªã„ã¨ãã«ãƒ¦ãƒ¼ã‚¶ãƒ¼ã‚’æ··ä¹±ã•ã›ã¾ã™ã€‚
+=item サãƒãƒ¼ãƒˆã—ã¦ã„るオペレーティングシステムã¯?
+
=begin original
-(=item What operating systems are supported?)
+(What operating systems are supported?)
=end original
-=item サãƒãƒ¼ãƒˆã—ã¦ã„るオペレーティングシステムã¯?
-
=begin original
Linux 2.6 or higher, OSX Tiger or higher, Windows XP or higher.
@@ -464,14 +462,14 @@
ã‚ãªãŸãŒãƒ‘ッãƒã‚’é€ã‚Œã°ã€ä»–ã®ã‚ªãƒšãƒ¬ãƒ¼ãƒ†ã‚£ãƒ³ã‚°ã‚·ã‚¹ãƒ†ãƒ もサãƒãƒ¼ãƒˆã•ã‚Œã‚‹ã§ã—ょã†ã€‚
+=item ãªãœFurlã¯ãƒãƒ£ãƒ³ã‚¯ã•ã‚ŒãŸã‚¢ãƒƒãƒ—ãƒãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ãªã„ã®ã§ã™ã‹?
+
=begin original
-(=item Why doesn't Furl support chunked upload?)
+(Why doesn't Furl support chunked upload?)
=end original
-=item ãªãœFurlã¯ãƒãƒ£ãƒ³ã‚¯ã•ã‚ŒãŸã‚¢ãƒƒãƒ—ãƒãƒ¼ãƒ‰ã‚’サãƒãƒ¼ãƒˆã—ãªã„ã®ã§ã™ã‹?
-
=begin original
There are reasons why chunked POST/PUTs should not be used in general.
@@ -506,14 +504,14 @@
ã“れらã®è¦å› ã§ãƒãƒ£ãƒ³ã‚¯ã•ã‚ŒãŸãƒªã‚¯ã‚¨ã‚¹ãƒˆã‚’使ã†ã®ã¯äº‹å®Ÿä¸Šä¸å¯èƒ½ã§ã™(サーãƒãŒHTTP/1.1をサãƒãƒ¼ãƒˆã—ã¦ã„ã‚‹ã¨ã‚ã‹ã£ã¦ã„ãªã‘ã‚Œã°)。
ãã®ãŸã‚ã€ã“ã®æ©Ÿèƒ½ã®ã‚µãƒãƒ¼ãƒˆã¯é«˜ã„プライオリティã§ã¯ã‚ã‚Šã¾ã›ã‚“。
+=item 到é”ã—ãŸãƒ¬ã‚¹ãƒãƒ³ã‚¹ã®å†…容をã©ã®ã‚ˆã†ã«ä½œã‚Œã¾ã™ã‹?
+
=begin original
-(=item How do you build the response content as it arrives?)
+(How do you build the response content as it arrives?)
=end original
-=item 到é”ã—ãŸãƒ¬ã‚¹ãƒãƒ³ã‚¹ã®å†…容をã©ã®ã‚ˆã†ã«ä½œã‚Œã¾ã™ã‹?
-
=begin original
You can use L<IO::Callback> for this purpose.
@@ -533,14 +531,14 @@
$furl->put( "http://127.0.0.1:$port/", [ 'Content-Length' => $len ], $fh,
);
+=item gzip/deflate 圧縮ã•ã‚ŒãŸã‚³ãƒŸãƒ¥ãƒ‹ã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã‚’使ãˆã¾ã™ã‹?
+
=begin original
-(=item How do you use gzip/deflate compressed communication?)
+(How do you use gzip/deflate compressed communication?)
=end original
-=item gzip/deflate 圧縮ã•ã‚ŒãŸã‚³ãƒŸãƒ¥ãƒ‹ã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã‚’使ãˆã¾ã™ã‹?
-
=begin original
Add an B<Accept-Encoding> header to your request. Furl inflates response bodies transparently according to the B<Content-Encoding> response header.
@@ -551,7 +549,7 @@
=begin original
-(=item How do you use mutipart/form-data?)
+(How do you use mutipart/form-data?)
=end original
@@ -587,14 +585,14 @@
パッãƒã‚’é€ã‚‹ã“ã¨ãŒã§ãã‚‹ãªã‚‰ã€L<Furl>ã§ãƒã‚¤ãƒ†ã‚£ãƒ–ã®multipart/form-dataサãƒãƒ¼ãƒˆã¯åˆ©ç”¨å¯èƒ½ã§ã™ã€‚
+=item Kee-Alive ã‚’ã©ã†ã‚„ã£ã¦ä½¿ã†ã®ã‹ã¨HEADメソッドã§ã¯ä½•ãŒèµ·ãã‚‹ã®ã‹?
+
=begin original
-(=item How do you use Keep-Alive and what happens on the HEAD method?)
+(How do you use Keep-Alive and what happens on the HEAD method?)
=end original
-=item Kee-Alive ã‚’ã©ã†ã‚„ã£ã¦ä½¿ã†ã®ã‹ã¨HEADメソッドã§ã¯ä½•ãŒèµ·ãã‚‹ã®ã‹?
-
=begin original
Furl supports HTTP/1.1, hence C<Keep-Alive>. However, if you use the HEAD
@@ -647,7 +645,7 @@
=begin original
-(=item Why does Furl take longer than specified until it returns a timeout error?)
+(Why does Furl take longer than specified until it returns a timeout error?)
=end original