Re: CallsOnline fix

Gary Austin ( (no email) )
Wed, 9 Apr 1997 19:13:42 -0400

If you don't require a license with the emerald product until they go over
500 then put the same limit on the other. Seems logical.

----------
> From: Dale E. Reed Jr. <daler@iea.com>
> To: RadiusNT@emerald.iea.com
> Subject: Re: CallsOnline fix
> Date: Wednesday, April 09, 1997 6:51 PM
>
> Phil Heller wrote:
> >
> > Or maybe implement a severe authentication delay after x
authentications.
> > You could also use some wacked out registry keys to prevent 'at' from
> > executing radius.exe.
> >
> > Just some thoughts. Maybe you could make the unregistered version only
> > capable of attaching to MS Access ODBC sources. Then the severe delays
> > will be inherent.
>
> Severe delays could be seen as a problem with the product. It would
> be annoying to work with a product which delays its responses,
> especially
> in an environment where a delay in a response is seen a down server. :(
>
> I'm thinking just a limit to the number of users might be in order.
> Maybe somethine around 25 or 50. Maybe as high as 100. That would
> be an easy way to go.
>
> --
> Dale E. Reed Jr. (daler@iea.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.emerald.iea.com
>
> ----------------------------------------------------------
> RadiusNT Mailing List listserver@emerald.iea.com