minimal documentation fixes
This commit is contained in:
parent
7228f15ebe
commit
8d47ecdfe4
@ -1,13 +1,13 @@
|
|||||||
= Architecture of uHub =
|
= Architecture of uHub =
|
||||||
|
|
||||||
uHub is single threaded and handles network and timer events using the
|
uHub is single-threaded and handles network and timer events using the
|
||||||
libevent library.
|
libevent library.
|
||||||
For each state there is a read event (and sometimes a write event) and timeout
|
For each state there is a read event (and sometimes a write event) and timeout
|
||||||
event in case an expected read (or write) event does not occur.
|
event in case an expected read (or write) event does not occur.
|
||||||
|
|
||||||
|
|
||||||
== Protocol overview ==
|
== Protocol overview ==
|
||||||
uHub use "speak" the ADC protocol, which works in short as follows:
|
uHub "speaks" the ADC protocol, which works in short as follows:
|
||||||
(C = client, S = server aka uHub).
|
(C = client, S = server aka uHub).
|
||||||
|
|
||||||
C: HSUP ADBASE
|
C: HSUP ADBASE
|
||||||
|
@ -31,7 +31,7 @@ The hub should send a packet containing the token back:
|
|||||||
'IECH {token} {host:port}', aswell as the same message via TCP.
|
'IECH {token} {host:port}', aswell as the same message via TCP.
|
||||||
|
|
||||||
If the client receives the message via UDP, it should now be able to determine the type of NAT.
|
If the client receives the message via UDP, it should now be able to determine the type of NAT.
|
||||||
If the client receives the message via TCP only it knows it has a firewall blocking icomming communication.
|
If the client receives the message via TCP only it knows it has a firewall blocking incomming communication.
|
||||||
If the client does not receive the message, it should assume a firewall is blocking all UDP communication,
|
If the client does not receive the message, it should assume a firewall is blocking all UDP communication,
|
||||||
and resume in passive mode.
|
and resume in passive mode.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user