I see most people request small webspace and large transfers, I'm requesting the inverse of this.
Requirements:
* I need at least 1.5GB, 2GB would be preferable in webspace.
* As for bandwidth 100MB/month.
* Support for large file sizes(my largest file is 37MB, so 40MB would be enough). Having said that, the 37MB file would not be downloaded, its only a support file kept in the directory. Most files are under 10MB, with the clear majority sized between 100KB-5MB.
* Not too many file extension restrictions
* The abililty to host a forum and/or guestbook
* rsync support - This is a show stopper. As I am constantly adding things, I need to be able to just transfer the differences between the directory I have and the directory on the hosting server.
What I can offer in return:
Not many web hosters both free and paid offer rsync as a method for transferring files. The thought of offering shell access scares most of them, as well as the security considerations. However, rsync does not need to be run through a shell or terminal, it could be run inside the browser via a frontend/wrapper and accessed through the normal user control panel. In this regards I could help with
* The setup of the rsync client
* The setup of a rsync frontend that is then accessable from within the user's control panel
* Writing of HOWTOs, tutorials, guides both Windows & Linux(and possibly even MacOSX) for the users on how to use rsync to transfer their files from their machines to the webhost.
This would set your hosting apart from the others. Also it would make your users very happy, especially the ones that regularly add new content to their websites. Happy users should mean a happy webhost as well.
What is rsync?
rsync is a program that is used for file transfers. rsync updates only files that have changed, so you do not need to retransfer all your data whenever you run rsync. It only mirrors new/changed files, and it can also delete files from the webhost that have been deleted on the content server. In addition to that it can preserve permissions and ownerships of mirrored files and directories.
To illustrate the point, if you create a 100MB file and then use rsync to transfer it across to a webhost. Then change one byte of the file, somewhere in the middle, and then rerun rsync. Fantastic - if one byte in the file changes, rsync will only transmit the relevant changed block. Now insert 5 bytes at the start of the file. This means that the entire file is shifted to the right by 5 bytes. Normally, a block level incremental backup algorithm (like those found in drive imaging programs) will actually need to backup the entire file again because of the shift in data (every single block is affected). However, Rsync is correctly able to identify the shift. So we see here that 70kB was received, and 12kB was sent. Most of this data would have been checksums to try to detect what part of the file changed. Still an outstanding result! 12kB sent compared to 100MB. So overall, rsync is quite simply a sound choice for bandwidth efficient block-level delta incremental data transfers.
Requirements:
* I need at least 1.5GB, 2GB would be preferable in webspace.
* As for bandwidth 100MB/month.
* Support for large file sizes(my largest file is 37MB, so 40MB would be enough). Having said that, the 37MB file would not be downloaded, its only a support file kept in the directory. Most files are under 10MB, with the clear majority sized between 100KB-5MB.
* Not too many file extension restrictions
* The abililty to host a forum and/or guestbook
* rsync support - This is a show stopper. As I am constantly adding things, I need to be able to just transfer the differences between the directory I have and the directory on the hosting server.
What I can offer in return:
Not many web hosters both free and paid offer rsync as a method for transferring files. The thought of offering shell access scares most of them, as well as the security considerations. However, rsync does not need to be run through a shell or terminal, it could be run inside the browser via a frontend/wrapper and accessed through the normal user control panel. In this regards I could help with
* The setup of the rsync client
* The setup of a rsync frontend that is then accessable from within the user's control panel
* Writing of HOWTOs, tutorials, guides both Windows & Linux(and possibly even MacOSX) for the users on how to use rsync to transfer their files from their machines to the webhost.
This would set your hosting apart from the others. Also it would make your users very happy, especially the ones that regularly add new content to their websites. Happy users should mean a happy webhost as well.
What is rsync?
rsync is a program that is used for file transfers. rsync updates only files that have changed, so you do not need to retransfer all your data whenever you run rsync. It only mirrors new/changed files, and it can also delete files from the webhost that have been deleted on the content server. In addition to that it can preserve permissions and ownerships of mirrored files and directories.
To illustrate the point, if you create a 100MB file and then use rsync to transfer it across to a webhost. Then change one byte of the file, somewhere in the middle, and then rerun rsync. Fantastic - if one byte in the file changes, rsync will only transmit the relevant changed block. Now insert 5 bytes at the start of the file. This means that the entire file is shifted to the right by 5 bytes. Normally, a block level incremental backup algorithm (like those found in drive imaging programs) will actually need to backup the entire file again because of the shift in data (every single block is affected). However, Rsync is correctly able to identify the shift. So we see here that 70kB was received, and 12kB was sent. Most of this data would have been checksums to try to detect what part of the file changed. Still an outstanding result! 12kB sent compared to 100MB. So overall, rsync is quite simply a sound choice for bandwidth efficient block-level delta incremental data transfers.
Comment