Little help deciding
I'm writing a class that allows you to browse through FTPs. The big difference from others is that it will have cache control. My delima is choosing how to cache it. I have 3 different options, and I am exploring all three. All 3 also have their ups and downs.
Here are my options:
- MySQL Database I have a MySQL database on my server (who doesn't nowadays?) that I can use. I believe this would be the easiest, if not fastest, way of doing it.
- Exact Copy My second option is to recreate every file in the filter (text files, images, files < X mb) in the exact structure as it is found on the FTP. Since I plan on releasing this class in the future, it would be good for people who don't have access to a MySQL Database.
- Flat file My third and final choice is probably the worst of them. Using a flat file that keeps the file structure and stores every bit of data. I have no experience with large-scale flat files, so I don't know how well it would work. But it is an option that may be looked into further unless I find a good reason not to.
If you all could help me choose that would be great. I'm leaning towards having an option of doing the first two since I am releasing this, or plan on it at least. The default would most likely be MySQL because it would put less strain on the server I believe. Thanks for the help, necrotic
Here are my options:
- MySQL Database I have a MySQL database on my server (who doesn't nowadays?) that I can use. I believe this would be the easiest, if not fastest, way of doing it.
- Exact Copy My second option is to recreate every file in the filter (text files, images, files < X mb) in the exact structure as it is found on the FTP. Since I plan on releasing this class in the future, it would be good for people who don't have access to a MySQL Database.
- Flat file My third and final choice is probably the worst of them. Using a flat file that keeps the file structure and stores every bit of data. I have no experience with large-scale flat files, so I don't know how well it would work. But it is an option that may be looked into further unless I find a good reason not to.
If you all could help me choose that would be great. I'm leaning towards having an option of doing the first two since I am releasing this, or plan on it at least. The default would most likely be MySQL because it would put less strain on the server I believe. Thanks for the help, necrotic
