Re: RE: SISC and JDK1.5?
Matthias Radestock <[email protected]>
| Newsgroups | gmane.comp.java.sisc.user |
|---|---|
| Message-ID | <[email protected]> |
Norman Gray <[email protected]> writes: > On 2006 Apr 11 , at 22.02, Scott G. Miller wrote: > >> The heap jar, while more easily >> resolvable, isn't randomly accessable, so it must be fully loaded into >> memory at a cost in time and space. Thats why its not in a jar by >> default. > > My mistake. I'd managed to convince myself that the sisc-heap.jar > was new, which of course is not the case. That doesn't mean it's not useful ... > Omitting boring details, the reason I was looking at this was that > the defaults-for-everything Context.execute() interface doesn't work > quite so neatly as it might within Tomcat, where, as you imply, the > location of the heap file isn't easily resolvable within findHeap(). I don't see anything wrong with just sticking the sisc-heap.jar into the web app. The overhead of reading the heap file into memory is dwarfed by tomcat. Problem solved. Matthias. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642