englishm has quit [Remote host closed the connection]
englishm has joined #mirage
_whitelogger has joined #mirage
gperetin has joined #mirage
boogie has quit [Remote host closed the connection]
jprakash has joined #mirage
boogie has joined #mirage
boogie has quit [Remote host closed the connection]
avsm has joined #mirage
avsm has quit [Read error: Connection reset by peer]
avsm has joined #mirage
avsm1 has joined #mirage
englishm has quit [Remote host closed the connection]
englishm has joined #mirage
avsm has quit [Ping timeout: 264 seconds]
englishm has quit [Remote host closed the connection]
englishm has joined #mirage
flasheater has quit [Read error: Connection reset by peer]
kmrhb_ is now known as kmrhb
boogie has joined #mirage
boogie has quit [Remote host closed the connection]
avsm1 has quit [Quit: Leaving.]
avsm has joined #mirage
avsm has quit [Quit: Leaving.]
rgrinberg has joined #mirage
tlockney_away is now known as tlockney
rgrinberg has quit [Quit: Leaving.]
philtor has joined #mirage
rgrinberg has joined #mirage
boogie has joined #mirage
andreas has quit [Quit: Leaving.]
englishm has quit [Ping timeout: 260 seconds]
brson has joined #mirage
rgrinberg has quit [Quit: Leaving.]
dsheets has quit [Ping timeout: 240 seconds]
rgrinberg has joined #mirage
djs55 has quit [Ping timeout: 260 seconds]
philtor_ has joined #mirage
brson has quit [Quit: leaving]
yomimono has joined #mirage
dbuenzli has quit [Ping timeout: 264 seconds]
djs55 has joined #mirage
boogie has quit [Quit: Leaving...]
<philtor_>
yomimono: you're the writer of: "Fitting the modular Mirage TCP/IP stack together" ?
liuw has quit [Ping timeout: 272 seconds]
<yomimono>
philtor_: yep (although there were many kind revisions)
* yomimono
stands by to accept blame
so has quit [Ping timeout: 245 seconds]
<philtor_>
So I'm trying to create an MQTT_client - it needs to do a socket connect and then read & write from it. I've been using Core's Tcp for this
<philtor_>
But to get it going in mirage...
<philtor_>
I need to do something like what's done in cohttp - the kind of thing described in your article.
<philtor_>
But I'm not sure (looking at cohttp) how this actually works.
<philtor_>
when I look at cohttp_lwt it seems that the network stuff has been abstracted into a Net module... but if I look at how that's put together, Net is actually mapped to Lwt_unix.
<philtor_>
Which seems like it wouldnt work with mirage.
<yomimono>
Huh, indeed. I remember puzzling over this and then just using create_connection from a stackv4 impl's tcpv4 .
so has joined #mirage
<philtor_>
Ok, that's kind of the conclusion I was coming to as well...
<yomimono>
that doesn't answer the question of "how is this even working", though.
<yomimono>
I know avsm's in the middle of a cohttp refactor because of something with conduit that I don't know the details on, so it may not go on working however it works now.
rgrinberg has quit [Quit: Leaving.]
<philtor_>
cohttp could be used outisde of mirage (as could my MQTT_client) so I'm thinking that somewhere in the functorization that mirage does everything gets connected to the right place.
tlockney is now known as tlockney_away
<philtor_>
Where is the implementation of create_connection ?
<yomimono>
philtor_: just a sec - attention divided at the moment
<philtor_>
ah, ok, I think I see it... that's plugged in by mirage depending on whether you choose direct or socket.