× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



 >Perhaps you could just allocate your 65 kb once and for all and reuse it?
If you can then avoid using "new" at all except at initialization time.

Good idea.  I wasn?t thinking of it from that perspective. 

>So the problem is that you need to convince the hardware vendor that you
behave correctly?  Why is this an issue?

I was of the same mind as you before I got involved. This isn't for a simple
consumer device but an application for a huge corporation [name purposely
withheld] MultiFunctional Device (MFD) and they put the code I develop
through the wringer - prodding and poking every possible area.  I have to
make a declaration in my manifest file for the maximum amount of memory my
applet will use, and if I go over that amount my applet fails their
verification process.  That is where the problem lies, because they are
stating I am using more memory than I believe my program is using. I could
just make the statement that my program uses up to 15MB, but they also
warned that if I pad my max mem usage by a lot that could also make me fail
verification.  So it is a tough spot to be in :-)

Aaron Bartell

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Thorbjørn Ravn Andersen
Sent: Wednesday, March 01, 2006 8:25 AM
To: Java Programming on and around the iSeries / AS400
Subject: Re: Garbage Collection - OutputStream

albartell wrote:

> There in lies the problem. The hardware vendor that this is for is 
> making
>
>statements saying I am consuming way more than my applet should be 
>allowed, but I am looking at it thinking that I am not using more than 
>65k at a time and it is instead the JRE on the device that is causing 
>GC to be delayed until the last possible moment.
>  
>
Perhaps you could just allocate your 65 kb once and for all and reuse it?
If you can then avoid using "new" at all except at initialization time.

So the problem is that you need to convince the hardware vendor that you
behave correctly?  Why is this an issue?

--
  Thorbjørn
--
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.