[Ekiga-devel-list] [THREADNESS] H.323 endpoint



Hi,

I wondered: <<what does h323.cpp does which makes it linked with the gtk+ lock? >>

The answer is : it doesn't use gtk+, but merely uses gmconf, which we decided to protect with our big lock.

Why does it use gmconf, then ?
(1) to initialize itself with defaults (fast start, H245 tunneling, early H245)
(2) to decide the DTMF mode
(3) to decide whether to forward to whom after how long.

We could perhaps just put (1) and (2) as arguments of the creation of the object (perhaps with some notifiers to handle configuration changes at runtime -- but outside of that file, called in the gtk+ thread).

For (3), I would push the decision outside that file, to a piece of code which would decide what to do mostly independantly from the protocol (does the user care about protocols? Unfortunately no, or skype wouldn't be hype).

More ideas later, I'm hungry ;-)

Snark

PS1: the headers from h323.h and h323.cpp don't use the right name for the files.
PS2: "reason" is a magic value!




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]