On Tue, 2008-06-17 at 10:34 -0400, Carolyn Beeton wrote: > > -----Original Message----- > > From: Scott Lawrence [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 17, 2008 9:27 AM > > > > What reads alarmDef.xml ? If it's just sipXsupervisor, > > that's all that I meant. > > sipXsupervisor reads it, and some day sipXconfig will write it. > > > > > Kathy Eccles and I are getting started on a set of issues > > that will end up restructuring much of sipXsupervisor, so > > we'll need to be careful not to trip over each other on this... > > > > I'm trying to clean up the code so I can make an initial offering soon > (maybe this week). The Alarm Server stuff is fairly self-contained with > minimal hooks in sipXsupervisor.cpp and MonitoredProcess.cpp, so we > shouldn't be too much in each others' way (as long as you aren't doing > anything with the Reporter classes, which now move into the Alarm Server > part of sipXsupervisor rather than the process management part).
That does not sound like a problem (indeed, it's probably much better). -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
