http://lists.iptel.org/pipermail/semsdev/2008-March/002379.html)
- implemented a connection pool, used for SEMS->SER message xchange initiated
by SEMS; this pairs with SEMS' one-thread-per-session design and should
boost throughput, as it only used one main socket before
- added multi-threaded receiver, for SER->SEMS xchange, pairing with SER's
multiprocess design and moving from the single-listener 1st implementation.
git-svn-id: http://svn.berlios.de/svnroot/repos/sems/trunk@1076 8eb893ce-cfd4-0310-b710-fb5ebe64c474
is now done 'automatically' by ser.
- b/f: when loading plugins, bail out at 1st raised error (the DI plugins
were missed the first time); otherwise, the 'err' var gets overwritten and
startup carries on, wrongly
git-svn-id: http://svn.berlios.de/svnroot/repos/sems/trunk@613 8eb893ce-cfd4-0310-b710-fb5ebe64c474
- splits the interface to the outer world from the core:
- use binrpcctrl plugin for SASI interface, or
- unixsockctrl for the good old unix socket interface.
git-svn-id: http://svn.berlios.de/svnroot/repos/sems/trunk@568 8eb893ce-cfd4-0310-b710-fb5ebe64c474
Bogdan Pintea
Stefan Sayer
Raphael Coeffic