bus limits

[Havoc Pennington]

On Sun, 2004-08-15 at 14:39, Seth Nickell wrote:
> > So, I've recently ran into the limits of the system message bus when
> > stress testing hal - (basically unplugging 10 USB devices at once,
> > leading to 50+ message calls at nearly the same time). The way I
> > discovered this was that some of the method calls to the service was
> > rejected by the bus with the message 'The maximum number of pending
> > replies per connection has been reached'. This limit, though
> > configurable from the system.conf file, defaults to 32.
> 
> FWIW, this limit makes DBus nearly impossible to use for something
> like Storage. Limits just seem like a bad idea, is there another way
> to detect that the other side isn't picking up messages? Maybe some
> sort of mandatory heart beat?
> 

The goal isn't to see if the other side is picking up messages, the goal
is to limit memory that a given client can force the bus to allocate.

Havoc