whitequark 3a656c1529 Inject the current timestamp into Device::{transmit,receive}. ...

Various parts of smoltcp require an arrow of time; a monotonically
increasing timestamp. Most obviously this is TCP sockets, but
the tracer and the pcap writer devices also benefit from having
timestamps. There are a few ways this could be implemented:
  1. using a static Cell, global for the entire smoltcp crate;
  2. using a static method on Device;
  3. using an instance method on Device;
  4. passing the current timestamp into *Interface::poll.

The first two options are undesirable because they create a notion
of global clock, and interfere e.g. with mocking.
The third option is undesirable because not all devices are
inherently tied to a particular clock, e.g. a loopback device isn't.

Therefore, the timestamp is injected into both sockets and devices
through the *Interface::poll method.

2017-07-23 09:48:14 +00:00

..

client.rs

Update README to explain how the client example works.

2017-03-05 06:15:15 +00:00

loopback.rs

Inject the current timestamp into Device::{transmit,receive}.

2017-07-23 09:48:14 +00:00

ping.rs

Do not attempt to validate length of packets being emitted.

2017-06-24 11:42:32 +00:00

server.rs

Add a sinkhole to the server example.

2017-05-29 16:54:51 +00:00

tcpdump.rs

Inject the current timestamp into Device::{transmit,receive}.

2017-07-23 09:48:14 +00:00

utils.rs

Inject the current timestamp into Device::{transmit,receive}.

2017-07-23 09:48:14 +00:00