Johan Nilsson wrote:
The current interface allows you to create and initiate processors before or after scheduler::operator() has been called. Sometimes you even need to call create_processor() before and initiate_processor() afterwards.
Out of curiosity, why would one ever want to call scheduler::operator() before initiate_processor()?
This happens quite often. On system start-up you simply start a new scheduler in its own thread, without creating any processors beforehand. Processors are later created on demand, depending on external input. I've never worked in the telephony field but I could imagine that you might want to create a new FSM when a call is placed and destroy it later when the call ends. Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.