[EMAIL PROTECTED] wrote:
>
> They were in sync. I discovered I got the same message after I killed the
> server! I had been playing with my policy file before, and I had removed
> the allpermission that had been granted to jdkhome/lib/ext. When I put
> that back all my problems went away. The
Nathan,
>Whoa, Kornel... we disagree on very little, if anything. You're welcome
>to point out deficiencies in the sample implementation, and I hope I'm
>welcome to point out that it *is* a sample implementation (which is why
>there's a market for companies like TowerJ to create *real*
>implement
kornel c wrote:
>
> Dear Nathan,
>
> >But, such considerations aside, it is useful to understand what problems
> >are inherent versus what are implementation details. Some of Java's
>
> I do understand memory management. I just don't necessarily want to have to
> care about it in Java: Java is
They were in sync. I discovered I got the same message after I killed the
server! I had been playing with my policy file before, and I had removed
the allpermission that had been granted to jdkhome/lib/ext. When I put
that back all my problems went away. The permission thing seems real
screwy
Dear Nathan,
>But, such considerations aside, it is useful to understand what problems
>are inherent versus what are implementation details. Some of Java's
I do understand memory management. I just don't necessarily want to have to
care about it in Java: Java is advertised as an environment whic
kornel c wrote:
>
> Dear Nathan,
>
> >Be careful of getting too hung up on the numbers. Memory management is a
> >bit of an art, and different JDKs take different approaches to fitting
>
> It wasn't me who got hung up on the numbers, it was my OS. Hey, I wouldn't
> have even noticed the memory
Dear Nathan,
>Be careful of getting too hung up on the numbers. Memory management is a
>bit of an art, and different JDKs take different approaches to fitting
It wasn't me who got hung up on the numbers, it was my OS. Hey, I wouldn't
have even noticed the memory requirements for long had it not
kornel c wrote:
>
> >Java is a memory hog... it's not JBuilder, it's Java. I've found that
> >my system was pretty much useless for any Java work at 64M. When Linux
> >JDKs catch up with some of the improvements now being enjoyed in other
> >environments (like HotSpot), the situation should impro
>Java is a memory hog... it's not JBuilder, it's Java. I've found that
>my system was pretty much useless for any Java work at 64M. When Linux
>JDKs catch up with some of the improvements now being enjoyed in other
>environments (like HotSpot), the situation should improve.
I agree, It is the JDK
Java-Linux Developers and AnyJ
Supporters,
I just got this from the
developers of AnyJ, take a look at what will be in AnyJ 2.0 ( Spring 2000
Release Estimate ), oh GOD THIS LOOKS SWEET.
SNIP
-
We redesign the data model. There is a datastor
10 matches
Mail list logo
