Feature #4364
Updated by Anonymous almost 7 years ago
The Once Task #4289 is finished, the congestion control functionality should be ported from one specific consumer application to an API that is more easily usable by multiple applications. This task is only about a **simple** API which provides a **high-level reliable transport object retrieval** (like a file download or non-time sensitive video playback). Some references: See the description in: - Consumer-Producer API for Named Data Networking http://named-data.net/wp-content/uploads/2014/02/TR17-consumer-producer-API.pdf - A Practical Congestion Control Scheme for Named Data Networking http://conferences2.sigcomm.org/acm-icn/2016/proceedings/p21-schneider.pdf - The Cisco Libicnet API: https://wiki.fd.io/view/Libicnet This tasks involves deciding the details of the design.