more client-vs-server refactoring: servers-only shouldn't subscribe to storage announcements #344

Open
opened 2008-03-12 07:02:40 +00:00 by warner · 1 comment

The next step in our refactoring of clients and servers is to make it possible to run server-only nodes. These clientless nodes will publish themselves as storage servers, but have no need to subscribe to hear about other storage servers. This will reduce the load on the introducer slightly.

The next step in our refactoring of clients and servers is to make it possible to run server-only nodes. These clientless nodes will publish themselves as storage servers, but have no need to subscribe to hear about other storage servers. This will reduce the load on the introducer slightly.
warner added the
code
major
enhancement
0.8.0
labels 2008-03-12 07:02:40 +00:00
warner added this to the eventually milestone 2008-03-12 07:02:40 +00:00
warner added
code-network
and removed
code
labels 2009-03-08 22:12:28 +00:00
tahoe-lafs modified the milestone from eventually to 1.7.0 2010-03-12 23:47:21 +00:00
tahoe-lafs modified the milestone from 1.7.0 to soon 2010-06-16 03:54:04 +00:00

adding keyword p2p to tag tickets that have to do with the open question of "Is Tahoe-LAFS client-server or is it peer-to-peer?": [//pipermail/tahoe-dev/2012-July/007533.html]

adding keyword `p2p` to tag tickets that have to do with the open question of "Is Tahoe-LAFS client-server or is it peer-to-peer?": [//pipermail/tahoe-dev/2012-July/007533.html]
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#344
No description provided.