< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] RADIUS for reSIProcate/dum



I still don't think using the radius library should be the default - I
think most people will not be requiring radius support.    Keep in
mind
that we also support Visual Studio build environments - so having
#ifdef'd code to Disable/Enable radius support is required.  My
preference is still for option 1.

I agree with Scott here.

Daniel: I sympathize with your position about the growing number of questions for the various components, and I have some ideas about changes to the configure system to make this easier to deal with. I don't know when I'll have time to implement them, but I believe I can come up with something that retains the current level of flexibility without the same burden on users at configuration time.


For the moment, I will implement it with the existing method - but be warned, my complete B2BUA solution adds even more dependencies, including Java. I might release it separately so as not to over-complicate reSIProcate and this mailing list - any comments?

There is a saying that for every extra question you ask the end user during compile/install, half your users will be turned away...


--


-----------------------------------------------------------------------
Ready Technology Limited
http://www.readytechnology.co.uk
Incorporated in England and Wales, 4940731
Registered office: Devonshire House, 60 Goswell Rd, London, EC1M 7AD
-----------------------------------------------------------------------