On Wed, 2008-05-14 at 14:21 -0400, keccles wrote: > On Tue, 2008-05-13 at 15:41 -0400, Lih Tzeng wrote: > > > -----Original Message----- > > > From: keccles [mailto:[EMAIL PROTECTED] > > > > > > > Will this configuration flag be exposed via sipXconfig? > > > I was thinking NO, but I can be convinced otherwise. > > > > Could you please explain > > > > - who should set the configuration flag, > > - where this flag should be set, and > > - when this flag should be set? > > > I am looking for guidance about where to place the 3.10.2 config > parameter to force large requests onto tcp first, > > Unfortunately I was mistaken and optimistic about whether the stack > currently gets any outside configuration information. > > The plan is that the main branch will not have this configuration choice > because ALL large requests will try tcp first. > > So one possibility, if the config solution is too unappealing, is that > the 3.10.2 would always try tcp first for large requests.
+1 The configuration alternative is ugly: to get new configuration to the stack, you need to add a member variable for it to SipUserAgent, provide a default, add a method to change the default, and add code to every service to read a configuration item and then invoke the set method. Whether or not we do this change there, 3.10.2 is already going to have a bunch of fairly significant changes to fix problems; it's already going to need a full QA cycle. I don't think this changes that. -- 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
