Re: bpc_send semantics and per-channel application-specific data?

>  lemme just drop in the appropraite header file section here...  bp_wrapper.h
> 
> You hafta maintain the data yourself, but you can associate it with the 
> channel.
...
> extern void* bpc_get_channel_info(struct CHANNEL_INSTANCE *inst);
...
> extern void bpc_set_channel_info(struct CHANNEL_INSTANCE *inst,
> 				  void *data);

Excellent!  Anything like this available on a per-message basis?  For 
large messages, or when frames get fragmented, messages can make quite a 
few passes through pro_frame_available() and info about them has to be 
remembered somewhere.  I suppose it is possible that the beepcore code 
doesn't even have any per-message data structures to hang a pointer in, 
though, as it is really only the application that is going to care much 
about message-level stuff.

-------------------------------------------------------
-- David C. Niemi           Adeptech Systems, Inc.   --
-- Reston, Virginia, USA    http://www.adeptech.com/ --
-------------------------------------------------------



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php