<p dir="ltr">32 bit 'flags' field in protocol for every message, meaning of which is a private matter of sender & receiver?</p>
<div class="gmail_quote">On Aug 27, 2014 6:03 PM, "Thiago Macieira" <<a href="mailto:thiago@kde.org">thiago@kde.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wednesday 27 August 2014 10:41:02 Alban Crequy wrote:<br>
> I would prefer if the headers are not too difficult to parse if not<br>
> necessary. At the moment, the headers don't have any "body offset" field<br>
> to know where the body of the message starts. So any implementation<br>
> would need to parse the header completely, even if it is not interested<br>
> in everything. Adding a "(sv)" means there could be more variants to<br>
> parse recursively.<br>
<br>
So what do you recommend instead?<br>
--<br>
Thiago Macieira - thiago (AT) <a href="http://macieira.info" target="_blank">macieira.info</a> - thiago (AT) <a href="http://kde.org" target="_blank">kde.org</a><br>
Software Architect - Intel Open Source Technology Center<br>
PGP/GPG: 0x6EF45358; fingerprint:<br>
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358<br>
<br>
_______________________________________________<br>
dbus mailing list<br>
<a href="mailto:dbus@lists.freedesktop.org">dbus@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/dbus" target="_blank">http://lists.freedesktop.org/mailman/listinfo/dbus</a><br>
</blockquote></div>