See, the thing about this is, we're not just content to implement
something - we have to go all the way around the Horn and implement it
RIGHT. There are a couple three different ways to do this, but none
of them are foolproof, all of them are vulnerable to various problems
- wrongly restricting users due to PM or network problems, holes that
let people sneak through, etc. In order to actually implement it and
get it working properly, every time, to our satisfaction, we'd have to
do a whole lot more than "take a look at some of the patches... and
do it". I ran into this debate back when I worked for Xylogics, too,
and had a good, long, soul-affirming argument with one of the
development engineers back there before he convinced me of the
non-triviality of the task involved, given the caveat "let's do it
right the first time." The same arguments hold true for any NAS.
>
> I'm sure that most ISP's would be suing radius.
>
So, I've decided to ignore the innately amusing typo here...
Anyway, I think I can safely say that, all debate aside, the demand
for this feature is fair-to-middlin'ly huge, and it'd be pretty silly
of us not to get round to making a reality, however non-trivial it
is. It's just a matter of that one commodity our engineering folks
don't have an abundance of - time.
--G.
-- Benjamin D. Hutchins gryphon@livingston.com | ACHTUNG! Alle Servicearbeiten A Minion of Livingston Enterprises Texaport | sollten vom dazu qualifizierten BellNet 800-458-9966 -><- FAX 510-426-8951 | Servicepersonal ausgefuehrt www.livingston.com <*> Ride the Wild Rhino | werden.