Wire format examples

[Felipe Gasper]

> On Oct 17, 2024, at 9:09 PM, Link Dupont <link.dupont at mac.com> wrote:
> 
> 
> 
>> On Oct 17, 2024, at 17:00, Lawrence D'Oliveiro <ldo at geek-central.gen.nz> wrote:
>> 
>> On Thu, 17 Oct 2024 11:17:17 -0400, Robert Middleton wrote:
>> 
>>> ... the fact that you can have nested objects and varied lengths of
>>> data is what really trips me up.
>> 
>> And note that objects requiring greater alignment can occur inside
>> parent objects with lesser alignment requirements. So the only way to
>> know where the padding should be placed is to look at the message as a
>> whole.
> 
> In my exploration so far, this is by far the most opaque element of the whole marshaling format to me. I haven’t found a pattern yet that I can use to figure out when and where to pad the data buffer.

The standard documents it variously, as I recall, though I also had to do a fair bit of trial & error.

D-Bus doesn’t lack for implementations; you could look around at various ones for clarifications of the standard.

-FG