eivind.naess at gmail.com
Fri Nov 30 17:15:18 CET 2007
Just to add my 2¢ to the conversation above. Really what you'd want is
to make freeradius client code provide the possibility of using
select() in your own code and not a part of performing radius_auth()
where select() is buried in the code of send_server(). In this way you
can make your code more "even-driven". This is an area where I'd like
to make an improvement in the freeradius client code (just haven't got
to it yet due to though schedules at work).
However, what you may want to check out is the freebsd code for
libradius, I haven't tried so yet, but I believe I read somewhere that
it provides such an API where your application performs the select and
you call one of its API functions if that FD triggers.
API for libradius:
You should look into it and see if this API provide you the interface
that you need for your application.
On Nov 26, 2007 8:24 AM, Alan DeKok <aland at deployingradius.com> wrote:
> Veerendra wrote:
> > To convert the client code from synchronous to asynchronous, Do you mean
> > to say, I need to bypass 'select' call and the response from Radius
> > Server should be handled like an Interrupt. How do we achieve this.
> > Kindly comment.
> If you don't have experience doing network programming, this is not
> the place to learn.
> If this is important to you, perhaps you could sponsor someone to do
> the work.
> Alan DeKok.
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
More information about the Freeradius-Devel