yomimono

That was my first thought, but I ran into a wall thinking of how to do anything with that information (although we can certainly discover it on the ip/ether layer),...

@mor1 , we can do that easily with the stack-level abstractions (STACKV1) because we have a hashtable of the listeners in the record, but not so in modules like TCP...

I've been thinking about this, and I'm not sure when you'd want to have a stack connect to itself anyway. In UNIX-land you do this because you have processes that...

Unless anyone objects, I'd like to close this and the related pull request #132 as `WONTFIX` - I haven't heard any compelling reason to put the required work in to...

Yes, it also means that if the application wants to change anything about the listening logic during execution, it needs to disconnect and reconnect the device. I think that's not...

Hearing no objections, I'll implement this.

Maybe we could do some README Mad-libs (I think this is Consequences in BrE?): https://github.com/ddbeck/readme-checklist/blob/master/checklist.md

The README should, IMO: * include more information on what is implemented in `tcpip` currently and what is not. * have a map including information on how complicated bits of...

@talex5 , I think I remember you saying this project needed a better README - is there anything specific that you felt was missing?

Aw, I'm sorry to hear that. ppx_deriving looked like just the thing for a project I've just started on, and I was looking forward to working with it. Thanks for...