midd:traffic_scheduling:project_log
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
midd:traffic_scheduling:project_log [2009/04/28 12:14] perryk |
midd:traffic_scheduling:project_log [2009/04/28 22:56] perryk |
||
|---|---|---|---|
| Line 218: | Line 218: | ||
| ==== 04/28 ==== | ==== 04/28 ==== | ||
| - | PK - experimented with blocking and non-blocking socket member. With non-blocking I crashed my computer every time when I hammered the adapter but did not do this with blocking set. Flag must do something :). | + | PK - experimented with blocking and non-blocking socket member. With non-blocking I crashed my computer every time when I hammered the adapter but did not do this with blocking set. Flag must do something :). Later this day: First fully functioning version of new client / server. |
| + | |||
| + | PK - AB - meet for an hour for code review, status. | ||
| + | |||
| + | PK - a few more hours in. I added three more transmission "models" to the client: load,burst and random. I have replaced the processor based clock and am now using DateTime.Now.Ticks to make the code portable to Linux. This means same-machine/same-subnet RTTs are 0. I added the adapter cumulative loss/ooo counts. I added timestamps in acks. Have conclusive evidence that the blocking socket flag does nothing in UDP. | ||
midd/traffic_scheduling/project_log.txt · Last modified: 2009/05/15 14:55 by afbarnard
Page Tools
