[openbeosstorage] Re: Registrar-Based Notification Mechanism
- From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Tue, 18 Feb 2003 21:07:50 CET (+0100)
> "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> wrote:
> [...]
> > > Ah, yes, I see, so it should provide a Flatten() call that
> > > already
> > > defines the target handler - something it has to provide
> > > internally
> > > anyway. That should be very easy to do.
> > No, that's not what one would want. Setting the target of a
> > BMessage
> > (fTarget, fPreferred) can easily be done now using the friend
> > function
> > =5Fset=5Fmessage=5Ftarget=5F(). The point is to flatten the message
> > only once
> > and for each target set the respective handler in the flattened
> > data.
> > I
> > could imagine a private `static status=5Ft
> > BMessage::SendFlattened(const
> > void *data, size=5Ft size, BMessenger target,...)' that sets the
> > target
> > in the flattened data and sends it to the respective port.
>
> Again, you thought more than me... :-))
> Sure, that's exactly what one would want to have, but that again,
> would
> be easy to do, once BMessage is in place. Just a friend method that
> sets the target and calculates the checksum to complete the flattened
> buffer - that can be used by Flatten(), too (but only once, there).
Of course, of course, once BMessage is in place... :-O
CU, Ingo
Other related posts:
