@notjack checking in

I’ve started integrating net2/data into axon/tcp

to get a feel for the concrete API

Right now, I’m working to replace '(host port) arguments with authority structs

and doing a rough implementation in my local net2/data.rkt stub

Should be able to re-use some comments and unit tests, but mainly to help me understand what’s supposed to be happening inside net2.

@dedbox are you thinking about giving each axon process an address in the form of an authority? or just trying to reuse the structs for now?

Just using structs right now. That’s the smallest self-contained change I could think of.

It’s actually the right abstraction for axon/tcp.

that makes sense

maybe something with disposable would be another small self-contained change for making things easier

a way to automatically give an axon process a disposable value that’s cleaned up when the process shuts down

Port management in my codecs was a pain to get right. That’s the low hanging fruit.

yeah I think disposable could make that easier but there might be some work I need to do to make it “correct”

disposables right now only allow allocation and deallocation with breaks disabled

which isn’t correct for accepting a tcp connection

Heh I punted and kill connections when either side closes

I wrote some ideas down here: https://github.com/jackfirth/racket-disposable/issues/114