ocaml-eio-net/lib/addr/ at main · gazagnaire.org/ocaml-eio-net · Tangled

gazagnaire.org / ocaml-eio-net

0

Eio network backends and test helpers

0

ocaml-eio-net / lib / addr /

at main 3 files

Thomas Gazagnaire eio-net: report reset-class writev errors the Eio way 6d ago

eio-net: cross between Ipaddr and Eio addresses in one place Eio names an IP address by its raw octets; Ipaddr names one by a parsed type. Twenty-odd sites open-code the crossing, and two of them get it wrong: Cfdp_eio.connect and Ltp_eio.connect hand a host *string* straight to Eio.Net.Ipaddr.of_raw, which raises Invalid_argument on anything that is not exactly 4 or 16 bytes -- so both raise on the very call their own docs show ("127.0.0.1" is 9 bytes, not 4). eio-net.addr is that crossing, both ways, with tests. It is a sub-library so the carrier libraries above it gain no ipaddr dependency, and so a unikernel guest that only needs to name an address links nothing else. Cfdp and Ltp now parse a literal address and resolve a name, which is what their ~host argument always claimed to take.

2 weeks ago

eio-net: cross between Ipaddr and Eio addresses in one place Eio names an IP address by its raw octets; Ipaddr names one by a parsed type. Twenty-odd sites open-code the crossing, and two of them get it wrong: Cfdp_eio.connect and Ltp_eio.connect hand a host *string* straight to Eio.Net.Ipaddr.of_raw, which raises Invalid_argument on anything that is not exactly 4 or 16 bytes -- so both raise on the very call their own docs show ("127.0.0.1" is 9 bytes, not 4). eio-net.addr is that crossing, both ways, with tests. It is a sub-library so the carrier libraries above it gain no ipaddr dependency, and so a unikernel guest that only needs to name an address links nothing else. Cfdp and Ltp now parse a literal address and resolve a name, which is what their ~host argument always claimed to take.

2 weeks ago

eio-net: cross between Ipaddr and Eio addresses in one place Eio names an IP address by its raw octets; Ipaddr names one by a parsed type. Twenty-odd sites open-code the crossing, and two of them get it wrong: Cfdp_eio.connect and Ltp_eio.connect hand a host *string* straight to Eio.Net.Ipaddr.of_raw, which raises Invalid_argument on anything that is not exactly 4 or 16 bytes -- so both raise on the very call their own docs show ("127.0.0.1" is 9 bytes, not 4). eio-net.addr is that crossing, both ways, with tests. It is a sub-library so the carrier libraries above it gain no ipaddr dependency, and so a unikernel guest that only needs to name an address links nothing else. Cfdp and Ltp now parse a literal address and resolve a name, which is what their ~host argument always claimed to take.

2 weeks ago