Nelson Minar writes:
> javares. Info is at http://gee.cs.oswego.edu/dl/javares/
The archive seemed to cover the first two weeks only?
> There's room for a good project here. There are some partial solutions
> now, JRes is probably the best known one.
The web site referred to in one of the ar
> > javares. Info is at http://gee.cs.oswego.edu/dl/javares/
>The archive seemed to cover the first two weeks only?
No, that's the full archive. My impression is a lot of people are
interested in the problem but not many people are working on it.
>>There's room for a good project here. There are
If you're interested in Java resource management, I encourage you to
carry on the discussion on a mailing list I run for just that purpose,
javares. Info is at http://gee.cs.oswego.edu/dl/javares/
There are lots of people who are interested in this problem - real
time folks, people running untrus
"Daniel W. Dulitz x108" wrote:
> Rob Clark writes:
> > Here's a crazy idea: the whole problem, as I see it, arises because
> > the JVM's garbage collector only knows of one resource pool, the
> > heap, when in fact there are other resource pools outside the JVM
> > that it should also concern its
Rob Clark writes:
> Here's a crazy idea: the whole problem, as I see it, arises because
> the JVM's garbage collector only knows of one resource pool, the
> heap, when in fact there are other resource pools outside the JVM
> that it should also concern itself with. [...]
>
> For example, sun could
Here's a crazy idea: the whole problem, as I see it, arises
because the JVM's garbage collector only knows of one resource pool, the
heap, when in fact there are other resource pools outside the JVM that
it should also concern itself with. Say, for example, you implement
a class, FooBar, that
