Re: [capnproto] Random access clarified

2023-09-19 Thread Johannes Dröge
Dear Kenton, Thanks for taking the time for those detailed answers, I really appreciate it! Though most information is available elsewhere in more technical formats, it's not always giving starters those answers in a comprehensible way. Design-wise, capnp really seems outstanding, and my

Re: [capnproto] Random access clarified

2023-09-05 Thread 'Kenton Varda' via Cap'n Proto
On Tue, Sep 5, 2023 at 6:08 AM Johannes Dröge wrote: > Great, thanks for the clear statement! > > I have some follow-up questions now: > > 1) How is the memory usage patter for the deserialization of such members > when they are accessed (either from disk or in memory). I suppose that the >

Re: [capnproto] Random access clarified

2023-09-05 Thread Johannes Dröge
Great, thanks for the clear statement! I have some follow-up questions now: 1) How is the memory usage patter for the deserialization of such members when they are accessed (either from disk or in memory). I suppose that the accessed element must be converted to a hardware-specific

Re: [capnproto] Random access clarified

2023-09-04 Thread 'Kenton Varda' via Cap'n Proto
Hi Johannes, Yes, it applies to list indexing. -Kenton On Mon, Sep 4, 2023 at 10:43 AM Johannes Dröge wrote: > Hi there! > > The FAQ states *"*Random access*:* You can read just one field of a > message without parsing the whole thing". *However, does that also apply > to List indexing*? I