🚀 go-pugleaf

On Wed, 01 Dec 1999 17:29:44 +0100, tluyben wrote:

> "John P. McGrath" wrote:
> 
> > You could also hunt down the threads and do a thread.stop()
> > on them.
> 
> I did, it is not working. These are native threads and they
> cannot be stopped (if you can, please tell me how ;-)

Hmmmm... I guess not.  I tried it with no luck either.  The AWT-Event 
thread died gracefully, but the AWT-Windows thread refused to budge.

> > I am curious -- Why are you using a Toolkit from a servlet?
> 
> I need to load gif and jpg images and createImage with arrays. 
> I need Toolkit for this. I have an example on the web where
> they created a counter with a servlet.
> This thing also never ends; I mailed them, and they never noticed.
> Except that NT got slower and slower until they had to restart.
> They thought this was a Win problem (I thought so until we moved
> to Linux and Solaris). Under Unix the servletrunner keeps going,
> gobbling up more resources while running. It never crashes, but
> it makes the system unusable by taking 20 mb mem with every 4
> threads spawned, so in the end the system is unusable.
> 
> If you know a way out of using Toolkit then this would be cool!

Have you checked into third party libraries?  There are some out there 
that handle a variety of graphics formats, and I would think they would 
work without using a Toolkit.  [ I find the idea of using a Toolkit from 
the server side is a little disquieting. ]

-- 
John P. McGrath
<JPMcGrath@fast.net>
<jpm@nscs.fast.net>