12-28-2016, 07:08 AM
(This post was last modified: 12-28-2016, 07:12 AM by qwerasd205.)
(12-27-2016, 11:17 PM)Apuly Wrote: Or we make it simpler:You don't seem to understand that all that "overhead" is necessary.
Total success:
A: This is a protocol request for protocol X
B: Affirmative
B online but does not use protocol X:
A: This is a protocol request for protocol X
B: Denied: protocol not supported
B is not online:
A: This is a protocol request for protocol X
B: ...
B is online but A isn't reachable:
A: This is a protocol request for protocol X
B: Denied: not reachable
When designing these protocols, you must keep in mind that there's very limited bandwidth and extremely high delay.
The amount of overhead that your protocol has is so ridiculously high, sending a single packet would take a couple of minutes.
It's important to get rid of as much overhead as possible, and I think that my implementation has as little as would be practicable.
The pings at the start are to check that both hosts are alive and reachable by the other host. Acks are needed to avoid major failure by packet loss. "denied not reachable" doesn't make sense because it has to ping to see if it can reach A in the first place.
I put a lot of thought in to it.
Also, assuming, say, 12 routers between the two hosts (which would be a lot), it takes 5 seconds to process a packet in a router meaning 1 minute to send the packet from A to B. Then, to establish a connection with my photo between A and B using protocol X with Y version, it will take 9 minutes, assuming no dropped packets, but if a packet is dropped the connection doesn't need to start form square one and it will only add a little over 1 minute to the time it takes to establish a connection.
This is my signature.