| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
|
Hi Scott, Thank you for your answer. I will have a look at Thread Pool in repro. At the moment I cannot say if it meets the needs
for this implementation. Regarding client library I thought to ace-radius (http://ace-radius.sourceforge.net),
but honestly I think that it should be reviewed before using it in Resiprocate. For example in version 0.9.2 it does not use anymore a thread pool (up to version 0.8.0 it used ACE framework), so it
is necessary to re-introduce a thread pool concept anyway. I think that it could be a good starting point if I decide to implement a small radius client library (just that part
needed for digest authentication). At this moment I am working on this idea in my free time, so I do not have much time to spare. I hope to give good news to all subscribers as soon as possible (it would mean that I would have had time...). Best regards, Dario. From: slgodin@xxxxxxxxx [mailto:slgodin@xxxxxxxxx]
On Behalf Of Scott Godin Hi Dario, Daniel Pocock implemented the freeradius-client stuff, so I'm not sure about windows support for it. Nor do I know of any Windows centric radius clients. So not much help there - sorry. However I'd like to point out that we would love to see the contribution into a resip branch. I would also like to point out that repro has a Thread Pool concept you could re-purpose if there was any hope of having this solution be usable
by platforms other than windows (see: Dispatcher, Worker and WorkerThread - these are candidates for a move into rutil). Scott On Wed, Oct 1, 2014 at 8:54 AM, Dario Bozzali <Dario.Bozzali@xxxxxxxxxxx> wrote:
|