On Fri, 2009-02-27 at 18:37 +0000, Ted Gould wrote: > Checking capabilities requires a round trip on DBus. Which could be > delayed by the notification daemon being busy. It definitely will be if > everyone check capabilities all the time. For the number of times that > people change notification daemons, I think it's better to check once. > > The correct way to implement it would be to attach the name owner and > then handle the case where the name owner is destroyed as it drops off > the bus. But, those patches would get rather large. Again, I think > this is a pretty minor usecase. > By "busy" you mean that it has hung, don't you? I highly doubt you could spam notify-osd (or any other notification daemon) enough to make it hang. -- Chow Loong Jin
-- Liferea shouldn't include actions if notification server doesn't accept them https://bugs.launchpad.net/bugs/328606 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
