I honestly don't think this is true for a couple of reasons:
1) Livingston uses the same tree code for all ComOS
2) Some people have modified 1.x Radius code they can't/haven't
migrated to 2.0 yet.
A couple of things that I continue to point out about Radius 2.0 is
that many of the features which Livingston claims (I assume this is
marketing, again) that is Radius 2.0 is really just a ComOS upgrade
that does have anything SPECIFIC to do with Radius 2.0, besides
a dictionary update. Updating your 1.x dictionary gives you many of
these Radius 2.0 features. The only one I am still haven't looked
into is menuing.
RadiusNT has had for a LONG time most of the Livingston Radius 2.0
features, including caching and many of the speed enhancements.
Our ODBC capabilities is still one of the best interfaces to a
Radius server on any platform (flexability and power).
-- Dale E. Reed Jr. (daler@iea.com) _____________________________________________________________________ Internet Engineering Associates | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com