midd:traffic_scheduling:project_log
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
midd:traffic_scheduling:project_log [2009/03/23 22:35] afbarnard created, included all previous content |
midd:traffic_scheduling:project_log [2009/03/29 17:28] perryk |
||
|---|---|---|---|
| Line 74: | Line 74: | ||
| PK - Created UDP plug-in. Server is sinking them. Next step is still real time capture on the server. Had to modify the TCP plug-in to slow it down. TCP wants to buffer up and send as few packets as possible. I want as many packets as possible so had to add about 100 millisecond delay between sends. | PK - Created UDP plug-in. Server is sinking them. Next step is still real time capture on the server. Had to modify the TCP plug-in to slow it down. TCP wants to buffer up and send as few packets as possible. I want as many packets as possible so had to add about 100 millisecond delay between sends. | ||
| + | |||
| + | ==== 03/23 ==== | ||
| + | |||
| + | AB - Worked on project wiki site. Created main page, reorganized existing content, uploaded proposal. | ||
| + | |||
| + | ==== 03/29 ==== | ||
| + | |||
| + | Have real time capture on server working. Was a little more difficult than expected as the server doesn't have a complete picture of who is sending to it. It builds a time-based partner dictionary and filters packets based on who is in the dictionary. If no packets have been sent or received with a partner, the partner times out and is removed from the filter dictionary. Next step is to provide a data exchange mechanism between client and server where by one tells the other what it's packet history is. | ||
| + | |||
midd/traffic_scheduling/project_log.txt ยท Last modified: 2009/05/15 14:55 by afbarnard
Page Tools
