On Fri, 2010-03-26 at 08:37 -0400, Beeton, Carolyn (Carolyn) wrote:
> I've been looking for a post-4.2 project, and came upon XX-4628, the
> next step in the supervisor \-> child communication strategy devised
> by Woof and partly implemented in 4.0.  The idea was that the
> supervisor would make a stdin pipe to each child before forking it,
> and could then write commands to this pipe such as "configuration
> changed".
>  
> If we continue down this road, then it would make sense to have a
> service skeleton for all C++ and Java services to use so that the work
> to manage the pipe is only done once.  The C++ projects already have
> the beginnings of this framework, in SipXecsService.cpp (which
> currently does only a bit of log level and file path work).  I would
> like to extend SipXecsService to do all the logfile and signal
> handling, and this new stdin handling if we continue with that, and
> then create an equivalent for the Java projects.
>  
> The first configuration change which I would like to get is log level
> changes on the fly.  I think we could get this for all C++ services
> pretty easily, since the log levels are already parsed and set in the
> SipXecsService class, and worry about more complicated config changes
> later.
>  
> In light of certain recent discussions about configuration change
> tracking, I am not sure if these changes are still desired, though I
> think having a service framework has merit in its own right.
>  
> So can I get some community feedback on
> - extending SipXecsService framework to include more common service
> issues, such as logfile management, signal handling
> - creating such a framework for Java projects
> - implementing the supervisor stdin pipe as a way of communicating
> config changes to child processes

Excellent idea Carolyn.


_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to