Hi Kenton, Thanks for your email and congratulations on the launch! Looks really cool!
> It'll probably take the least time overall if I can manage to take an initial > crack at it first in C++ and just power through things, rather than have > other people try to implement the spec as written and then have to ask a lot > of questions when there's confusion. Sure, that makes perfect sense. I’m thinking it’s probably best if we push back the meeting until after you’ve laid down the foundations for 3PH, at which point we can kill two birds with one stone: changes to the spec based on your C++ implementation, and considerations for the Go implementation. Kenton, I don’t want to pressure you into meeting any sort of deadline, but I also don’t want this project to fall through the cracks. Is it ok if we tentatively reschedule for e.g. Friday October 16th at 13:00 PDT and make any adjustments as-needed? (Ross, Ian, does that date also work for you?) Cheers, Louis > On Sep 30, 2020, at 15:29, Kenton Varda <[email protected]> wrote: > > Sorry for the very slow response this time. We had a big launch on Monday and > I haven't had much time to reply to e-mail. > > Incidentally that launch is vaguely relevant here. > > https://blog.cloudflare.com/introducing-workers-durable-objects/ > <https://blog.cloudflare.com/introducing-workers-durable-objects/> > > We built the infrastructure for this on Cap'n Proto. When you make a request > to a Durable Object, you're actually making Cap'n Proto RPC requests all they > way from the call site to the destination object. Since Durable Objects will > soon be able to migrate around the world, 3-party handoff is likely to become > important as old locations will need to forward requests to new locations. > > The Workers Runtime is written in C++, but we do have a fair amount of Go > code at Cloudflare, so it'd be neat if 3PH were supported there too. > > In any case, I'd like to start working on this soon, but I also have a big > pile of other things I need to work on so I'm not sure how much time I'll > have to dedicate. > > Based on my experience working on the RPC system in the past, I think it's > safe to expect that as we implement 3PH, we're likely to run into a bunch of > little spec issues. It'll probably take the least time overall if I can > manage to take an initial crack at it first in C++ and just power through > things, rather than have other people try to implement the spec as written > and then have to ask a lot of questions when there's confusion. I'm hoping to > get at least a few days to work on it maybe the week after next. > > As it happens I am available at 13:00 PDT (15:00 CDT) Friday if you still > want to chat then. > > -Kenton > > On Fri, Sep 25, 2020 at 10:59 AM Ian Denhardt <[email protected] > <mailto:[email protected]>> wrote: > Works for me. > > Quoting lthibault (2020-09-25 11:04:56) > > Friday October 2 at 13:00 PST (16:00 EST for Ian and myself) works for > > me. > > > > Ian, is that ok with you? > > > > Kenton, any chance we might count you in as well? > > > > - Louis > > > > On Friday, September 25, 2020 at 10:52:25 AM UTC-4 [email protected] > > <mailto:[email protected]> > > wrote: > > > > I'm available next Friday (Oct 2) from 1p PT onward. > > > > On Friday, September 25, 2020 at 7:36:07 AM UTC-7 lthibault wrote: > > > > Sounds good to me � looking forward to it. > > - Louis > > > On Sep 24, 2020, at 17:17, Ian Denhardt <[email protected] > > <mailto:[email protected]>> wrote: > > > > > > I just opened an issue: > > > > > > [1]https://github.com/capnproto/go-capnproto2/issues/160 > > <https://github.com/capnproto/go-capnproto2/issues/160> > > > > > > I believe Kenton is in Texas these days. For my part I could > > manage most > > > afternoons/evenings (eastern time) though Monday & Thursday > > afternoons > > > are bad. But if Ross and/or Kenton are interested in joining us I > > > suspect their schedules are much more constrained than mine. > > > > > > -Ian > > > > > > Quoting lthibault (2020-09-23 18:31:05) > > >>> Are you amenable to Jitsi Meet[1] instead of Zoom? > > >> That's totally fine. I've been meaning to ditch Zoom, anyway. > > >> > > >>> We should also perhaps reach out to Ross > > >> > > >> Absolutely. Would you be able to reach out to him? > > >> > > >> I think you and I are in the same time zone (I'm in New Haven, > > CT), and > > >> I believe Kenton and Ross are on the west coast, so maybe early > > early > > >> afternoon? > > >> > > >> Any particular preference for the day? > > >> > > >> Cheers, > > >> > > >> Louis > > >> > > >> On Wednesday, September 23, 2020 at 5:36:03 PM UTC-4 > > [email protected] <mailto:[email protected]> > > >> wrote: > > >> > > >> Quoting lthibault (2020-09-23 14:41:13) > > >>> How do you suggest we proceed? I'm thinking it might be useful > > to > > >> get > > >>> synchronized over a Zoom call since (a) I could benefit from a > > >> guided > > >>> tour of v3 and (b) my initial high-level questions about the > > Level > > >> 3 > > >>> protocol remain open. Would be cool if Kenton could join us too. > > >> :) > > >> I'd be up for a video call. Are you amenable to Jitsi Meet[1] > > >> instead of > > >> Zoom? We've been using it for the weekly Sandstorm office hours > > >> calls. > > >> We should also perhaps reach out to Ross; I know he doesn't have > > >> time to > > >> hack on it, but might still be interested in weighing in on > > design > > >> questions/offering advice. Want to open an issue re: level 3 on > > the > > >> Go > > >> implementation's issue tracker? Maybe we can coordinate the rest > > of > > >> this there. I know Ross is also on this mailing list, so he may > > see > > >> this > > >> anyway, but he'll definitely see it there. > > >> -Ian > > >> [1]: [1][2]https://meet.jit.si <https://meet.jit.si/> > > >> > > >> -- > > >> You received this message because you are subscribed to the > > Google > > >> Groups "Cap'n Proto" group. > > >> To unsubscribe from this group and stop receiving emails from it, > > send > > >> an email to [2][email protected] > > <mailto:capnproto%[email protected]>. > > >> To view this discussion on the web visit > > >> > > [3][3]https://groups.google.com/d/msgid/capnproto/7bdd072b-9496-4e52 > > <https://groups.google.com/d/msgid/capnproto/7bdd072b-9496-4e52> > > -afca- > > >> e105626e24b3n%[4]40googlegroups.com <http://40googlegroups.com/>. > > >> > > >> Verweise > > >> > > >> 1. [5]https://meet.jit.si/ <https://meet.jit.si/> > > >> 2. mailto:[email protected] > > <mailto:capnproto%[email protected]> > > >> 3. > > [6]https://groups.google.com/d/msgid/capnproto/7bdd072b-9496-4e52-af > > <https://groups.google.com/d/msgid/capnproto/7bdd072b-9496-4e52-af> > > ca-e105626e24b3n%40googlegroups.com?utm_medium=email&utm_source=foot > > <http://40googlegroups.com/?utm_medium=email&utm_source=foot> > > er > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Cap'n Proto" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to [7][email protected] > > <mailto:capnproto%[email protected]>. > > To view this discussion on the web visit > > [8]https://groups.google.com/d/msgid/capnproto/ed1fa9e0-362e-4041-adaa- > > <https://groups.google.com/d/msgid/capnproto/ed1fa9e0-362e-4041-adaa-> > > e482f6b3d402n%40googlegroups.com <http://40googlegroups.com/>. > > > > Verweise > > > > 1. https://github.com/capnproto/go-capnproto2/issues/160 > > <https://github.com/capnproto/go-capnproto2/issues/160> > > 2. https://meet.jit.si/ <https://meet.jit.si/> > > 3. https://groups.google.com/d/msgid/capnproto/7bdd072b-9496-4e52-afca- > > <https://groups.google.com/d/msgid/capnproto/7bdd072b-9496-4e52-afca-> > > 4. http://40googlegroups.com/ <http://40googlegroups.com/> > > 5. https://meet.jit.si/ <https://meet.jit.si/> > > 6. > > https://groups.google.com/d/msgid/capnproto/7bdd072b-9496-4e52-afca-e105626e24b3n%40googlegroups.com?utm_medium=email&utm_source=footer > > > > <https://groups.google.com/d/msgid/capnproto/7bdd072b-9496-4e52-afca-e105626e24b3n%40googlegroups.com?utm_medium=email&utm_source=footer> > > 7. mailto:[email protected] > > <mailto:capnproto%[email protected]> > > 8. > > https://groups.google.com/d/msgid/capnproto/ed1fa9e0-362e-4041-adaa-e482f6b3d402n%40googlegroups.com?utm_medium=email&utm_source=footer > > > > <https://groups.google.com/d/msgid/capnproto/ed1fa9e0-362e-4041-adaa-e482f6b3d402n%40googlegroups.com?utm_medium=email&utm_source=footer> > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:capnproto%[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/capnproto/160104957747.876.5192754664800499465%40localhost.localdomain > > <https://groups.google.com/d/msgid/capnproto/160104957747.876.5192754664800499465%40localhost.localdomain>. -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/8AEBE42F-A2EE-40F4-A352-AE26273C580D%40gmail.com.
