Changes between Initial Version and Version 95 of Ticket #68
- Timestamp:
- 2012-12-06T21:34:31Z (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #68
- Property Cc zooko killyourtv@… added
- Property Component changed from code to code-network
- Property Summary changed from One introducer = single point of failure to implement distributed introduction, remove Introducer as a single point of failure
- Property Keywords scalability availability introduction gsoc docs anti-censorship test-needed added
- Property Milestone changed from to soon
- Property Owner changed from somebody to lebek
-
Ticket #68 – Description
initial v95 1 I am quite sure you are aware of the problem that an introducer/vdrive server crash bringing everything down. I read your roadmap.txt but I didn't find anything specific to address this. May I suggest using introducers.furl and vdrives.furl where multiple entries can be usedand the information is updated to all introducers at the same time when a peer makes an update.1 I am quite sure you are aware of the problem [of] an introducer [...] crash bringing everything down. I read your roadmap.txt but I didn't find anything specific to address this. May I suggest using introducers.furl [...] where multiple entries can be used and the information is updated to all introducers at the same time when a peer makes an update. 2 2 3 3 Also, upon adding a new introducer, there should be a way to discover all the info currently on the existing introducer. I think I am making this part sounds more trivial than it is.