SwitchBoard - Revision history

Adamcolton at 23:21, 3 May 2016

2016-05-03T23:21:47Z

← Older revision		Revision as of 23:21, 3 May 2016
Line 28:		Line 28:

	This doesn't allow a user to directly register an onion route (the ID isn't big enough), so we'll end up needing a whole other service to do that unless we change ID to data and cap it at the size of a half-onion.		This doesn't allow a user to directly register an onion route (the ID isn't big enough), so we'll end up needing a whole other service to do that unless we change ID to data and cap it at the size of a half-onion.

			== Message Passing ==
			Messages will also move through the system. These include requests, nodes joining and nodes leaving.

			=== Bandwidth ===
			This is a challenge, a 1K message, once a second consumes 2.5G in a month.

			=== DDOS ===
			Even if we

	[[Category:Waxnet]]		[[Category:Waxnet]]

Adamcolton: /* Record */

2016-05-03T21:30:48Z

Record

← Older revision		Revision as of 21:30, 3 May 2016
Line 21:		Line 21:

	A bit abstract, but if I want some resource, I need to know what it's identifier. That's val. There may be a number of ways for me to get this resource. Each provider can register a service and ID to use on that service to request the resource.		A bit abstract, but if I want some resource, I need to know what it's identifier. That's val. There may be a number of ways for me to get this resource. Each provider can register a service and ID to use on that service to request the resource.

			The val cannot be requested though. You must have the Val to perform a put, but just the key to perform a get.

	=== Problems ===		=== Problems ===

Adamcolton at 20:04, 5 April 2016

2016-04-05T20:04:10Z

@@ Line 11: / Line 11: @@
 == Hole-Punching ==
 I want to avoid using Hole Punching as much as possible - it's slow and annoying. But even if it were required everywhere, a small number of "gateways" could serve a huge number of users. Once a user is connected to one other peer, that peer can act as the STUN server for yet other peers. And so, any peer that can be discovered via the DHT can be reached via hole-punching (barring sym2sym).
 [[Category:Waxnet]]

Adamcolton at 21:05, 4 March 2016

2016-03-04T21:05:31Z

← Older revision		Revision as of 21:05, 4 March 2016
Line 8:		Line 8:

	If we request to be connected to another node, it will return a messaging saying the request was received and is being processed. Later, it will return a message saying if the connection was successful or not.		If we request to be connected to another node, it will return a messaging saying the request was received and is being processed. Later, it will return a message saying if the connection was successful or not.

			== Hole-Punching ==
			I want to avoid using Hole Punching as much as possible - it's slow and annoying. But even if it were required everywhere, a small number of "gateways" could serve a huge number of users. Once a user is connected to one other peer, that peer can act as the STUN server for yet other peers. And so, any peer that can be discovered via the DHT can be reached via hole-punching (barring sym2sym).

	[[Category:Waxnet]]		[[Category:Waxnet]]

Adamcolton: Created page with "SwitchBoard is used to connect peers. == Structure == SwitchBoard is a DHT. A user connects through a gateway and then synchronises themselves to the DHT. Switchboard tracks ..."

2016-03-02T16:50:04Z

Created page with "SwitchBoard is used to connect peers. == Structure == SwitchBoard is a DHT. A user connects through a gateway and then synchronises themselves to the DHT. Switchboard tracks ..."

New page

SwitchBoard is used to connect peers.

== Structure ==
SwitchBoard is a DHT. A user connects through a gateway and then synchronises themselves to the DHT. Switchboard tracks who is connect and the information needed to connect to them (IP:Port and NAT Traversal data).

== Service ==
As a local service, it can say if we're connected to another node. Search for another node. Connect to another node.

If we request to be connected to another node, it will return a messaging saying the request was received and is being processed. Later, it will return a message saying if the connection was successful or not.

[[Category:Waxnet]]