- getFramedAveragePeerClockSkew() now returns a long (ms);
was a Long (s)
- Implement NTP-style clock slewing so the clock is adjusted
gradually
- Implement clock strata so we prefer better clocks
- Implement a timestamper in the transport so we will periodically
update the clock even if NTP is not working
This allows the router to converge the clock instead of simply
hoping the first connected peer is correct.
- Slow down NTP attempts after several consecutive failures
- Store and report UDP clock skews even for large values, so
a badly skewed local clock will be reported to the console
- Don't shitlist for NTCP clock skew if we don't know what time it is
- If NTP hasn't worked yet, have NTCP or SSU update the clock one time
- Include failed clock skew in NTCP skew vector if there aren't many connections
- Don't include NTCP clock skews for non-established connections
- Fix framed clock skew frame size
- Report framed clock skew even if for only one peer, if NTP hasn't worked yet
- Don't log RRD errors after clock adjustment
- Reduce min skew for console warning to 30s (was 45s)
- More Java 5 cleanups
- Fix status to show a disconnected network error rather than
clock skew or UDP error when disconnected
- Use peer clock skew rather than clock offset for determining
whether to display clock skew error, i.e. display what matters
* Transport: Rework peer clock skew method to always return a value
by falling back to router clock offset;
Fix possible AIOOBE and divide by zero; remove logging;
reduce min number of peers
- Switch all I2PThreads to I2PAppThreads
- Run an InternalSocket as well for the HTTP Proxy
* EepGet: Use InternalSocket
* Console: Change "depth" to "length"
