o Jeremy A [08/28/09 12:12]:
Stefan Sayer wrote:
first the plugins are loaded, then initialized, and then several
threads are started (session container, media processor, rtp receiver,
SIP server thread).
I will certainly implement the change you suggested. However, it appears
to me that the 'construction' of all the plugins is single threaded with
an ordering that does not reflect the order in the conf file. My
suggestion is that the ordering of 'construction' be determined by the
order in the sems.con file.
indeed, they are initialized not in order, in fact, that is grouped by
type (base plugins, session event handlers, DI component plugins,
logging facilities, application modules, ctrl interface), and in the
groups they are sorted alphabetically...
an advantage of loading them all first and then initialize is that you
can execute DI functions in onLoad.
we could change the onLoad order to the load_plugins order, but it does
actually not make sense to place calls before the other threads (RTP
receiver etc) are started.
Stefan
I also think an alternative sequence of forking the 'construction' of
all plugins may well be problematic.
Regards
Jeremy
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
--
Stefan Sayer
VoIP Services
[email protected]
www.iptego.com
IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
