Ok, the short and sweet. I am considering doing public redirects. I am not right now considering bandwidth or price, as I am more interested in features, then I can base what it may cost me off what is necessary to meet maximum community needs. Here are the basics, and you folks can offer any advice you can think of. Forget the idea of bandwidth right now or any other internet based limiting factors. Assume server is configured for maximum connections, and assume all files uploaded are compressed.
So number1 is:
1: All files uploaded must be compressed (will only allow file extension of UT3 compressed files to be uploaded)
2: Uploads to be done via anonymous FTP and then check for duplicate file names/sizes. If a file has the same name, different size, the we can assume that it's a new version of the file. I am sure a lot of you are like me and HATE having to deal with changing a file name in a config file for mutators and such.
3: The uploads are placed in a queue for approval before being moved to a standard web accessible directory
4: Files will be be distributed to multiple servers via rsync, so that no one server is loaded to the gills with connections, so to speak. Of course that is up to each server admin to use the closest redirect server.
Now, that is just that absolute base of what I am thinking. I have tons more ideas, but the core of it all is a basic public redirect service for those with either crap connections or low storage availability. Any ideas, thoughts, hints would be greatly appreciated.
Yes, I know this can turn into a rather large deal. As I said, forget any aspect except the basic premise of providing a place to upload files and serve as a public redirect. Thanks fellas!