a message header flag for interactive authentication?

[Alban Crequy]

On Wed, 27 Aug 2014 08:03:16 -0700
Thiago Macieira <thiago at kde.org> wrote:

> On Wednesday 27 August 2014 10:41:02 Alban Crequy wrote:
> > I would prefer if the headers are not too difficult to parse if not
> > necessary. At the moment, the headers don't have any "body offset"
> > field to know where the body of the message starts. So any
> > implementation would need to parse the header completely, even if
> > it is not interested in everything. Adding a "(sv)" means there
> > could be more variants to parse recursively.
> 
> So what do you recommend instead?

I have no real objections in adding a bit in the existing flag field,
along NO_REPLY_EXPECTED and NO_AUTO_START.

I would like a couple more examples than just the addressbook though.
And if the new bit is only for D-Bus method calls, what if the
addressbook emits D-Bus signals to signal some changes in a contact
details? In this case, I'm not sure the authentication scheme would work
without changing the D-Bus API.

Alban