Re: [Tsp-devel] Flooding the BB msg queue

[Eric Noulard]

2007/6/20, Eric Noulard <address@hidden>:
> 2007/6/20, Frederik Deweerdt <address@hidden>:
>
> >
> > My use case is more or less like sync, but I use the PID of the client
> > as mtype, so that I can tell several clients that value X vas
> > modified. Otherwise, only the first one that gets the msg is notified. If
> > one subscriber suddenly dissapears, the queue fills up and no one ever
> > gets the sync after a few messages.

One last (may be :)) thing,

Beware tha fact that we used message queue in order to achieve
"loose" synchronization.
That why:
- implementation does almost nothing if message queue is full.
- bb "server" usually don't care if someone received the message
  (that's why you need ACK from your listener if needed
   lib bb_provider may work this way, look for
BB_SIMPLE_MSGID_SYNCHRO_COPY_ACK)

If you want "real broadcast-like synchronization" I think you should go for
condition variable or semaphore ...

The synchronization is loose BY DESIGN.
If you need more may be you should add the feature as a
separate feature, evnetually built on top the existing one.

May be you can tell us the raw specification of what you need?
--
Erk