@dedbox This is great!

I’ve got some changes to the connector docs I’m working on that should hopefully make their details clearer

Also, note that transports care about authorities only, not full URIs. Both <http://foo.com:2233/resource1> and <http://foo.com:2233/resource1> could be retrieved over the same transport, since they use the same authority

Two URIs with different schemes can even be retrieved over the same transport, as happens with websocket URIs (<ws://foo.com> and http://foo.com)

although the websocket protocol has some weirdness to it

Lots of changes to the model. I’ve put the LaTeX source and a PDF snapshot into a github repo https://github.com/dedbox/racket-net2-model

@dedbox Thanks for all your interest in this project btw, collaboration is a great thing to have

minor update: I’m taking a brief break from net2 work to help samth out with some docker stuff for testing racket’s release process (see the https://github.com/samth/docker-racket-build repository)

I expect I’ll be spending time on net2 this coming weekend

@notjack thanks for the heads up