问候，Rozmaha。

回复你在2008年6月26日星期四的留言，23：19：48，

嘿，这么快的问题，什么是设置执行的好时机

时间使用set_time_limit如果我想上传说一个100 MB的文件。我知道带宽并且知道一切都很重要，但也许你可以给我一个好的号码，无论如何都可以。

1. set_time_limit与文件上传无关，除非你从脚本上传

文件（使用cURL ie）

请参阅
http://www.php.net/manual/en/info.co...max-input-time

代替。

2.将FTP用于这样的大文件。

-

真诚的你，AnrDaemon< an ******* @ freemail.ru>

6月26日晚上9点10分，AnrDaemon< anrdae ... @ freemail.ruwrote：

问候，Rozmaha。

回复你在2008年6月26日星期四23:19:48发来的消息，

嘿，这么快的问题，什么是设置执行的好时机

时间使用set_time_limit如果我想上传说一个100 MB的文件。我知道带宽并且知道一切都很重要，但也许你可以给我一个好的号码，无论如何都可以。

1. set_time_limit与文件上传无关，除非你从脚本上传

文件（使用cURL ie）

请参考http://www.php.net/manual/en/info.configuration.php#ini.max-input-time

。

2.使用FTP来处理这些大文件。


-

真诚的你，AnrDaemon< anrdae ... @ freemail.ru>

FTP很糟糕 - 出于很多原因。 HTTP [s]是一个更加明智的

协议，用于在任一方向上移动文件。为了***的

性能/安全性使用scp或rsync而不是ssh。


C.

C。 （ http://symcbean.blogspot.com/ ）写道：

6月26日晚上9:10，AnrDaemon< anrdae ... @ freemail.ruwrote：

>问候，Rozmaha。
回复你在2008年6月26日星期四23:19:48发来的消息，

>>嘿，所以快速提问，如果我想上传一个100 MB的文件，那么使用set_time_limit设置执行的时间是多少。我知道带宽，一切都很重要，但也许你可以给我一个好的号码，无论如何。

1. set_time_limit与文件上传无关，除非您从脚本上传
文件（使用cURL即）
请参阅http：// www.php.net/manual/en/info.configuration.php#ini.max-input-time
相反。
2。使用FTP来处理这些大文件。

- 真诚的你，AnrDaemon< anrdae ... @ freemail.ru>

FTP很糟糕 - 出于很多原因。 HTTP [s]是一个更加明智的

协议，用于在任一方向上移动文件。为了***的

性能/安全性，请使用scp或rsync over ssh。


C.

错了。传输文件时FTP速度更快，效率更高 -

，因为它是专门为它设计的。


我永远不会处理这么大的文件超过http - 它缺少一些好的

功能，例如恢复功能。然后是文本文件的新

行字符的转换。还有一堆其他的东西。


如果你想要安全，那就有sftp。


-

==================

删除x来自我的电子邮件地址

Jerry Stuckle

JDS计算机培训公司
js ******* @ attglobal.net

==================

Hey, so quick question, what would be a good time to set for execution
time using set_time_limit if I wanted to upload say a 100 mb file. I
know bandwidth and everything is important to know, but maybe if you
could give me a good number that works in any case.

Thanks

Greetings, Rozmaha.
In reply to Your message dated Thursday, June 26, 2008, 23:19:48,

Hey, so quick question, what would be a good time to set for execution
time using set_time_limit if I wanted to upload say a 100 mb file. I
know bandwidth and everything is important to know, but maybe if you
could give me a good number that works in any case.

1. set_time_limit has nothing to do with file uploads, unless you are uploading
files from your script (using cURL i.e.)
Refer to the
http://www.php.net/manual/en/info.co...max-input-time
instead.
2. Use FTP for such big files.
--
Sincerely Yours, AnrDaemon <an*******@freemail.ru>

On Jun 26, 9:10 pm, AnrDaemon <anrdae...@freemail.ruwrote:

Greetings, Rozmaha.
In reply to Your message dated Thursday, June 26, 2008, 23:19:48,

Hey, so quick question, what would be a good time to set for execution
time using set_time_limit if I wanted to upload say a 100 mb file. I
know bandwidth and everything is important to know, but maybe if you
could give me a good number that works in any case.

1. set_time_limit has nothing to do with file uploads, unless you are uploading
files from your script (using cURL i.e.)
Refer to thehttp://www.php.net/manual/en/info.configuration.php#ini.max-input-time
instead.
2. Use FTP for such big files.

--
Sincerely Yours, AnrDaemon <anrdae...@freemail.ru>

FTP sucks - for lots of reasons. HTTP[s] is a far more sensible
protocol for moving files in either direction. For the best
performance/security use scp or rsync over ssh.

C.

C. (http://symcbean.blogspot.com/) wrote:

On Jun 26, 9:10 pm, AnrDaemon <anrdae...@freemail.ruwrote:

>Greetings, Rozmaha.
In reply to Your message dated Thursday, June 26, 2008, 23:19:48,

>>Hey, so quick question, what would be a good time to set for execution
time using set_time_limit if I wanted to upload say a 100 mb file. I
know bandwidth and everything is important to know, but maybe if you
could give me a good number that works in any case.

1. set_time_limit has nothing to do with file uploads, unless you are uploading
files from your script (using cURL i.e.)
Refer to thehttp://www.php.net/manual/en/info.configuration.php#ini.max-input-time
instead.
2. Use FTP for such big files.

--
Sincerely Yours, AnrDaemon <anrdae...@freemail.ru>

FTP sucks - for lots of reasons. HTTP[s] is a far more sensible
protocol for moving files in either direction. For the best
performance/security use scp or rsync over ssh.

C.

Wrong. FTP is much faster and more efficient when transferring files -
because that''s what it is specifically designed for.

I would never handle such large files over http - it''s missing some good
features, such as resume capability. Then there''s the conversion of new
line characters for text files. And bunches of other things.

And if you want security, there''s sftp.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attglobal.net
==================