Historic:Synced servers: Difference between revisions

From SoylentNews
Jump to navigation Jump to search
No edit summary
m (Admin moved page Synced servers to Historic:Synced servers)
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{archival}}
Altslashdot would be run on a number of independent web servers, which would utilise some syncing protocol in order to serve exact copies. The syncing would likely be cheap, because the number of such servers would be substantially smaller that the number of users.
Altslashdot would be run on a number of independent web servers, which would utilise some syncing protocol in order to serve exact copies. The syncing would likely be cheap, because the number of such servers would be substantially smaller that the number of users.


The possibility of running such a server would be open, in a hope, that a large number of these would eventually be created. "Hub" sites might exist, that would redirect to the least--loaded servers.
The possibility of running a server would be open, in a hope, that a relatively large number of these would eventually be created. "Hub" sites might exist, that would redirect to the least--loaded servers.


Beside sharing hosting cost, the architecture would enable the exclusion of a rogue server.
Beside sharing hosting cost, the architecture would enable the exclusion of a rogue server.
== Comments  ==
I'm no programmer, but isn't this how USENET worked?
Yes, it is similar, but we would need much more than Usenet, like safe user base and moderation. And it all would need to be tunneled through corporate firewalls, which often allow only web traffic.
:USENET was a great way to distribute postings, but it had the flaw that every USENET provider had to carry copies of all the messages for all hosted groups, leading to a lot of redundancy and a huge bandwidth burden syncing updates every day. If I were doing USENET today, I'd have designated "home" servers for each group, with all other servers caching updates for subscribers. [[User:Mfnickster|Mfnickster]] ([[User talk:Mfnickster|talk]])

Latest revision as of 05:20, 4 December 2024

Obsolete Page
This page is obsolete and only retained for archival purposes.

Altslashdot would be run on a number of independent web servers, which would utilise some syncing protocol in order to serve exact copies. The syncing would likely be cheap, because the number of such servers would be substantially smaller that the number of users.

The possibility of running a server would be open, in a hope, that a relatively large number of these would eventually be created. "Hub" sites might exist, that would redirect to the least--loaded servers.

Beside sharing hosting cost, the architecture would enable the exclusion of a rogue server.

Comments

I'm no programmer, but isn't this how USENET worked?

Yes, it is similar, but we would need much more than Usenet, like safe user base and moderation. And it all would need to be tunneled through corporate firewalls, which often allow only web traffic.

USENET was a great way to distribute postings, but it had the flaw that every USENET provider had to carry copies of all the messages for all hosted groups, leading to a lot of redundancy and a huge bandwidth burden syncing updates every day. If I were doing USENET today, I'd have designated "home" servers for each group, with all other servers caching updates for subscribers. Mfnickster (talk)