Bullshit it is simple. You need to look at it from our side - we have
all kinds of users with very wide ranges of scalability needs.
Every patch out there that I have seen has major failure modes. How do
you address having more than one RADIUS server when it falls over? What
about when the PM reboots? What about when a RADIUS sever crashes? What
about network outages or blocks? How does it scale to large users with
hundreds of PMs and several RADIUS servers?
>themselves. Of course I understand that they don't have infinite time,
>but a comittment to doing this soon would be nice.
It won't be that soon.
>I don't like the idea of losing money because people are sharing accounts
>though.
So why aren't you billing them for each simultaneous login? Can be easily
done right now with stock RADIUS and many other sites are doing this.
'Unlimited use' doesn't mean 'login as many times as you like' - put it
right in the contract and start billing. You might be surprised at how
fast people change their passwords when they get huge bills. And if they
don't pay they're deadbeats and you shut off access.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 6920 Koll Center Parkway #220, Pleasanton, CA 94566