> -----Original Message----- > From: mike [mailto:mike503@xxxxxxxxx] > Sent: Friday, August 08, 2008 4:36 PM > To: Per Jessen > Cc: php-general@xxxxxxxxxxxxx > Subject: Re: Re: PUT vs. POST (was: php File upload) > > On 8/8/08, Per Jessen <per@xxxxxxxxxxxx> wrote: > > > I am not for or against either, I'm just looking for the right > argument > > for PUT support as it seems to be lacking (and I've never found > myself > > in a situation where PUT was the solution). > > I need to accept files of various sizes - up to 2GB, maybe even more > (if it can be supported) - videos, code samples, zips, pdfs, anything. > > They're coming from various geographies - so slow unreliable > connections must be factored in. > > HTTP upload even with -large- files on a fast connection can be > spotty, due to how many systems are in place between client -> server. > There is no resume either with straight browser upload... My buddy is/was hosting a free licensed-music service that needed "segmented" uploads. I wrote a Java applet that communicates with a "receiver" PHP page to upload the file in segments rather than all at once. I got it to successfully upload an MP3, but a few bytes were missing from the destination file. I'll try to go digging through the "receiver" code and see if I can't find something to post that may give you guys a push in (hopefully) the right direction. I had to use Java for the simple fact that PHP by itself cannot access the local file system in a way that allows for the partial loading of files. If I/we get the source to work, 2GB, 4GB, the contents of the library of congress... all will be feasible. More news at 11, Todd Boyd Web Programmer
