Task #2557
open
- Assignee set to Steven Collison
- Status changed from New to In Progress
- % Done changed from 0 to 10
- Estimated time set to 4.00 h
ndn-udp-simple used IpFacesHelper which used IpFaceStack. Neither of these modules seem to be working. Should I try to port both of them to make the example work? It looks like a lot of work to get both of them working.
It looks like the old IpFaceStack did a lot of the socket communication on behalf of the Tcp/Udp faces. Ex: IpFaceStack registers a receive callback with with ns3 socket. Right now I'm registering the receive callback from within the UdpFace. Should I change my current UdpFace implementation to conform to this? Or should I not follow what IpFaceStack does?
Would it be a better idea to try to hack the example without using IpFaceStack?
You need to make it work in one way or another :)
If you don't want to follow the way it was done before, propose your design and we can comment on that. You has to have an entity that manages Udp/Tcp faces (= listens for incoming connections for TCP, processes incoming UDP packets from new remote addresses). IpFaceStack is one, but not the only option for that. NFD codebase has different design principle that you can follow (this would be UdpChannel and TcpChannel with UdpFactory and TcpFactory to create the channels).
I think I underestimated the number of changes that need to be made to integrate the new IpFaces! For now I'll try to work with IpFaceStack. I'm a little busy right now(big surprise) but I should have another update later in the week.
I've spent some time adapting the IpFaceStack and the ndn-simple-udp example. I've got it to successfully compile and run, though I'm not sure about the correctness.
A Couple questions:
- Assignee changed from Steven Collison to Yuanzhi Gao
- Status changed from In Progress to New
- Assignee deleted (
Yuanzhi Gao)
- Target version changed from 2.1 to 2.7
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by