This is no longer applicable to RadiusNT 2.5 and higher, since
the accounting and authentication threads act seperately with
this own ODBC connection (whereas 2.2 shared the same ODBC
connection between the two pieces).
No RADIUS implementation will ever be 100% accurate doing concurrency
control via accounting, and thats why many RADIUS vendors do not
support it. We are working on next generation concurrency contorl
that doesn't rely totally on RADIUS and will not prevent concurrency
unless its real-time verifiable.
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com