Re: B_STAT_CHANGED

Ingo Weinhold <bonefish-CFLBMwTPW48UNGrzBIF7/[email protected]> wrote:
> On Thu, 19 May 2005, Philippe Houdoin wrote:
> > Ingo Weinhold <bonefish-CFLBMwTPW48UNGrzBIF7/[email protected]> replied:
> >> On Thu, 19 May 2005, Axel [iso-8859-15] Dörfler wrote:
> [...]
> > You can add extra attributes to the old B_STAT_CHANGED message to 
> > indicates:
> > - that other changes are highly expectable in the future (file not 
> > closed yet)
> Yep, just a boolean "intermediate" field.

Okay, so that's how it'll be done, unless I hear a good argument 
against it :-)

> > - which stat field had changed (for R2?)
> That's already implemented. :-)
> We have added a "fields" field to the notification message that is a 
> mask 
> indicating what stat fields have changed.

BTW I noticed that R5 and our BMessage don't know when they were built 
or sent. In Dano/Zeta, every message contains a timestamp which I find 
very useful. It would be easy to add this to our KMessage, but there is 
probably no way to add it to BMessages without changing their flattened 
structure.

Bye,
   Axel.



-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_idt12&alloc_id344&op=click