That's a very very very big file.

Post #316,746 by static 11/4/09 5:46:50 PM Reply	That's a very very very big file. As Greg says, there are two php.ini settings, upload_max_filesize and post_max_size. You also need the PHP form to send MAX_FILE_SIZE hidden field (the upload code checks it's there) with an appropriate value. And you also have to consider the implications of sending that large a file through PHP: you will need to raise the memory and execution time limits. And then you may need to raise the memory limits in Apache itself. Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.
Post #316,764 by crazy 11/5/09 7:30:13 AM Reply	Yup Most people don't connect just how big >2GB means. And it this case, it might go to 10 gb. Really. And I need to receive and process between 2 and 20 of these a day, intermixed with little ones.
Post #316,801 by static 11/5/09 6:02:58 PM Reply	I'd be looking at an SFTP or SCP solution. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.
Post #316,805 by boxley 11/5/09 6:45:42 PM Reply	same here
Post #316,819 by crazy 11/6/09 6:23:16 AM Reply	I wish No matter HOW dumb the file size is, we are trying an initial setup that minimises client side setup. The client could be way away, out of our jurisdiction. If we want to allow them to send the file, we have to make it as simple/standard as possible. That even includes using a java/java script side library for a different protocol since they might be killed on THEIR internal firewall for those protocols. On the other hand, it is still an option. But to start with, everything is 3 high speed local network router hops away. Which of course is a best case scenario. And we'd like to use the functionality locally anyway, so it's fine to add better/more secure transfers after we do this initial usage. I totally expect large trasnfer to fail all the time if this design was rolled out to the outside world.
Post #316,820 by Another Scott 11/6/09 7:49:50 AM Reply	Is chopping up the file into < 2 GB chunks an option? If the main problem is the file size limit, can you have the client machine chop the file into < 2 GB chunks (automatically, in the background) before it is sent? I'm thinking of calling something like Zip Chunker in the background, sending the pieces, and then reassembling them on your end. How one would do that via PHP is left as an exercise for the reader. (IOW, I'm waving my hands around madly.) http://www.jibbensof...com/utilities.cfm Just a thought. Good luck. Cheers, Scott.
Post #316,821 by crazy 11/6/09 8:02:17 AM Reply	Unlikely But possible. I'll save it for Phase II Thanks
Post #316,850 by scoenye 11/6/09 7:52:51 PM Reply	You can bet on that Yesterday, I was about to comment on the 20 x 10GB/day load you were expecting, but then figured this was on a LAN. That would be a sustained 23 Mb/s for 24 hours straight. Even if your download speeds allow it, the uploader better have deep pockets...
Post #316,875 by crazy 11/7/09 11:46:01 AM Reply	Other way around Office with 2 net connections, no idea how fast. Server in the server room,I have to process these files by sending them offsite (via internet) to service provider who does stuff with them, and sends them back. So triple the actual usage. Oh, and the the final files have to be sent back to the client via ftp pushes or web pickup. Quadruple it. Current usage has client or us ftp slinging these around already, but current usage is about 30GB per week. So: #1: Let the curent clients upload them via self-serve website. #2: As we add clients, add bandwidth as needed. The additional processing will pay for it, or, I'll move to a cohosted box that has cheaper bandwidth. All my stuff is running in VMWare instances (both Linux and Windows), so the physical location should not matter.
Post #316,854 by boxley 11/6/09 9:52:13 PM Reply	a place I used to work used sftp to send files from taiwan to mumbai, tokyo to the states. Once we talked them thru the initial connection setup, no prob
Post #316,876 by crazy 11/7/09 11:48:17 AM Reply	Been there, done that But this should ultimately go to an end user at a corporate desktop behind the corporate firewall and the end user may not have the slightest ability to get the ports opened up. Been there done that too. So I'll avoid the ssh protocols if possible.
Post #316,936 by Mycroft_Holmes_Iv 11/8/09 10:55:49 PM Reply	I'd seriously consider putting up an FTP server for anonymous uploads. FTP can handle the 2GB, iirc. (The OS should be able to handle it) Only allow uploads, no browsing. (Effectively a drop box)
Post #316,953 by crazy 11/9/09 7:41:08 AM Reply	How would you handle the client side? Imagine a mid-level corporate person, non-techie, gopher type. His executive marketing boss told him to grab a file off the network and upload it to us after logging in to our web site. He is clueless about anything having to do with computers other than his 3 applications he lives in. He certainly can't initiate a windows level ftp session as a separate process outside the web site interaction. So how would I trigger a controlled FTP upload? I am unaware of any seemless browser usage at this point, but I'd be happy to be wrong. This is one of many possible people, all trying to do the same thing.
Post #316,956 by boxley 11/9/09 8:54:54 AM Reply	build a web based wrapper for it.
Post #316,966 by crazy 11/9/09 11:15:31 AM Reply	How convenient I used to have a boss like that. Nice general high level descriptions. He sure looked smart when he could even use them in the correct context. You want to be a bit more specific - ON THE CLIENT SIDE!
Post #316,973 by folkert 11/9/09 12:10:58 PM Reply	I KNOW! Use a PHP script for it!
Post #316,977 by boxley 11/9/09 12:58:42 PM Reply	start here http://www.enterpris...doc/devguide.html all the customer needs to do (from your description) is non tech people need to easily upload a large file to you, so a browser based app would ask what file the customer wishes to send including how to find it (attachement function generic) click "yes this is the file I weant to send" browser client needs to tell customer status of upload (activity bar) and a notification of when it is finished (pop box "we're done!") now get a little fancier and provide a toolbar icon and make the whole thing a plugin. does that help a little bit?
Post #317,024 by crazy 11/10/09 2:22:04 AM Reply	Help a lot Thanks
Post #317,043 by Mycroft_Holmes_Iv 11/10/09 8:49:36 AM Reply	That's a possibility... others include (not limited to...): building a shell script (.bat file) to upload the files. Put an icon on their desktop and anything in the SendToXYZ folder gets uploaded. a web page that lives locally (file:\c:whatever) that loads the file up (give them the ability to browse for the file) a small program that does the connection for ftp. Either java/C#/C++, etc. Again, it's an icon on their desktop.
Post #317,088 by crazy 11/10/09 5:07:42 PM Reply	No icons No desktops. Web users.

Welcome to IWETHEY!