On Dec 13, 2007, at 6:28 AM, Rolf Huehne wrote: > > Because an "OUT OF MEMORY" error freezes Jmol and the standard user > most > likely won't take a look at the Java console it would be really > good to > be able to warn the user at least. > Since memory requirements and availability differ largely between > users > I would prefer a solution that would orient at the individual > configurations and files loaded. >
as a simple kludge, you could use a server-side filter to check the pdb file size before loading it into Jmol. then give the user an alert if the file size exceeds the standard java memory allocation. this would cover the majority of users, I think. (an option for expert users would be to set a cookie indicating their java allocation, and thus avoid the dialog. if you know how to query for that info directly, you could make this more sophisticated.) just a thought. tim -- Timothy Driscoll em: [EMAIL PROTECTED] Virginia Bioinformatics Institute ph: 540-231-3007 Bioinformatics I: M-1 im: molvisions Washington St., Blacksburg, VA 24061 04-16-07. We will not forget you. ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Jmol-users mailing list Jmol-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jmol-users
