Sorry it’s a crappy email client called Outlook.. I will see if I can make it friendlier for you guys.
Otherwise deal with it.... -----Original Message----- From: Krzeminski, Damian (BL60:9D30) Sent: Wednesday, April 01, 2009 6:22 PM To: Campbell, Alfred (BL60:9D30) Cc: [email protected] Subject: Re: XCF-3521 Please do not top-post on the list... Alfred Campbell wrote: > So it sounds like we should maybe enter an issue to track the immediate > notification and put it into the post 4.0 bucket? > > Sound reasonable? > > Al Yeah - Let's definitely open a new issue. If there is an non-intrusive patch soon it might even get in 4.0 but I am not putting this in current sprint. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Krzeminski, Damian > (BL60:9D30) > Sent: Wednesday, April 01, 2009 10:19 AM > To: [email protected] > Subject: Re: [sipX-dev] XCF-3521 > > Andy Spitzer wrote: >> Woof! >> >> On Tue, 31 Mar 2009 20:39:08 -0400, Alfred Campbell <[email protected]> >> wrote: >> >>> If someone makes a dialing plan change there is a potential they could >>> miss the restart message. Meaning they won’t restart the service and >>> think the change took effect. Although its only like a 15 second >>> window it could happen. >>> >>> Anyone else concerned at all? >> As I outlined before, I don't like the "delay" on notifying of restart. >> >> >> I think the "restarted needed" message should show up instantly on any >> change that requires it. >> >> However, the actual writting of the changes to the config files CAN be >> delayed for some time, in order to not thrash on multiple changes. >> >> But once the user presses "restart", any changes not yet written should >> be written, and then the service restarted. >> >> > > Makes sense and it does solve the 2 conflicting needs nicely. > I do not think it's easy to implement but I might be missing something > obvious. If someone wants to give it a try go for it. > > That said: I do not think people make a dial plan change and then log out > within 15 seconds all the often. I do not think we have to tackle it now. > D. > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
