Guest (newbie) wrote:
This would only be appropriate for static content, though you could use it to carry the static portion of a dynamic site.
Isn't it posible that servers (posible mirrors) share their DB contents and link them to have it up to date?
Um, I don't know about you, but as a webmaster, there's a lot of superfluous database stuff that I REALLY wouldn't want to let off my server. I mean, if someone wanted to log into my site, would it be a good idea to have the username and password on a peer as opposed to the server? Even if it was a hash of the password (you'd have to be silly for it not to be a hash), you still couldn't gaurantee that it's authentic... well you could, but there's still the issue of how much of your database do you want to distribute?
You could do some very application specific implementations of twink serving dynamic content, like some sort of twink-aware forum software on a twink-aware webserver - where users on a popular site wouldn't just download the threads/posts that you're looking at, but also popular ones. But that's not a very general application.
And in the case of a blog or a CMS, again, you'd have to be very careful about trusting a peer. How can you gaurantee that it's a true copy of the central server, and more importantly how can you be sure that the peer is holding an up-to-date version... Although I'm sure some creative use of RSS feeds could come in useful there.
Actually, if the central server would naturally be the tracker, so it would be in charge of versioning control anyway... I can see this becoming an interesting problem.
However, trying to manage dynamic sites would be a pain in so many different ways... Some hypothetical
situations could be: if it's a server module (like an apache module) would it be aware of the server-side languages? Could it handle data generated by cgi modules (as opposed to apache modules - some run php as a cgi module because it can be more secure)? For intelligent version control it would need to know when the database is updated etc... would that be through the module generating the page, or would it need its own direct 'awareness' of the database? In which case drivers.
So yeah, I can see why TheShadow would want to keep it to static pages.