summaryrefslogtreecommitdiff
path: root/README_v6
diff options
context:
space:
mode:
authorerdgeist <>2007-01-27 16:06:13 +0000
committererdgeist <>2007-01-27 16:06:13 +0000
commitc094695add94493ab46d535b6fca1801efa127c2 (patch)
tree6dd0f7ee88c5a4a2951a44f9f7f2bd873880b22f /README_v6
parent65675cd4daf5c5d26b13e32d1a8779aa8b689f88 (diff)
account downloaded before early returns
Diffstat (limited to 'README_v6')
-rw-r--r--README_v66
1 files changed, 3 insertions, 3 deletions
diff --git a/README_v6 b/README_v6
index 72d25a3..6a5a82a 100644
--- a/README_v6
+++ b/README_v6
@@ -1,8 +1,8 @@
1Q: Why is there no v6-support in opentracker? 1Q: Why is there no v6-support in opentracker?
2 2
3A: Although I tried very hard, implementing v6 right now would be a terrible waste of bandwidth, there is no compact format for v6 addresses, so instead of 3A: Although I tried very hard, implementing v6 right now would be a terrible waste of bandwidth, there is no compact format for v6 addresses, so instead of
4answering "d5:peers6:AAAAPPe" I'd have to send "d5:peersld2:ip39:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA4:port2:PPPPeee" for a single peer. Even if there was a 4answering "d5:peers6:AAAAPPe" I'd have to send "d5:peersld2:ip39:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA4:port2:PPPPeee" for a single peer. Even if there was a
5compact mode, v6 addresses still would eat up thrice the memory, v4 addresses take. This, however, wouldn't be a show stopper. 5compact mode, v6 addresses still would eat up thrice the memory, v4 addresses take. This, however, wouldn't be a show stopper.
6 6
7Other problems concern efficient peer selection for obviously v6-capable peers and how to select peers for non-v6 clients. v6 addresses eat up more memory on the 7Other problems concern efficient peer selection for obviously v6-capable peers and how to select peers for non-v6 clients. v6 addresses eat up more memory on the
8host, too ;) 8host, too ;)