While the Java people are doing nice things and releasing all sorts of
code, Lucent says "not ready yet" on fixing problems in Radius 2.1,
COMOS 3.7.2 for the PM2, and 3.8.2 for the PM3. Maybe some reallocation
of resources is called for?
In the notes below, someone was thinking about betting his business by
switching to a FIVE MONTH old beta. I was recommending against that. A
conclusion that one might draw is that Radius 2.1 is a very broken piece
of code that they couldn't fix in five months.
I don't work for Lucent RABU wrote:
>
> On Fri, 19 Feb 1999, Roy wrote:
>
> >
> > The "beta" is over five months old. Given the lack of progress, I am
> > not sure if I would switch to it.
> >
> > All Livingston seems to be working on these days is Java Tools. Its
> > like rearranging the deck chairs on the Titanic.
>
> Well, look at it this way Roy, I doubt the Java development team works on
> RADIUS (I could be wrong), and maybe they are just having much better
> success?
>
> Many issues on specific problems should be taken to support@livingston.com
> where you could latch onto the respondant to keep you informed. That way
> you'll most likely be communicating with someone who knows about the issue
> you have.
>
> --
> Aloha from Paradise,
>
> Sherwood
> Got Clue? If so: ISPF! The Forum for ISPs by ISPs, <http://www.ispf.com>
>
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
> Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>