Woof wrote: > On Tue, May 4, 2010 at 10:25 AM, George Niculae > <[email protected]> wrote: > > Or I could grab the Acegi source code and build a sipx > custom library > > containing the new classes. Of course, including original Acegi > > copyrights... (if I'm not wrong, we had this approach some time ago > > for HtmlUnit library, before upgrading to 2.5) > > I think that's overkill for the few changes you made. And it > would most likely mean that upgrading to a new version of > Acegi would be more difficult in the future.
Agreed. We should be able to get a change submitted into Acegi, so we can just use it in the future. So, I think we need to: 1. Copy the file for 4.2.1, as George has done, but include the Acegi headers. 2. Work into the Acegi project to get the changes into their codebase. 3. When #2 is done, switch to it. (Not in 4.2.1.) Does that make sense? -Paul [email protected] _______________________________________________ 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/
