On Sunday 28 March 2004 01:11, Miguel wrote: > Egon wrote: > >> The code is currently commented out because it will not work inside > >> the Applet. It is a security violation for an untrusted applet to try > >> to talk to another web server. > > > > Would it be an option that the code is skiped over when the applet is > > run? That is, a passive disabling of the code? > > Yes, but we will need to make a few changes to the code. > > For example, the code references the URI class, which did not exist in > Java 1.1.
Ah... did not realize that... mmm... > Therefore, the applet will not even load on Microsoft IE & old > Netscape. > > dadml.jar adds 28K to the size of the applet. And, does it need the XML > parser? I am not saying that we shouldn't do it, but we should think about > it. gnujaxp-onlysax.jar would do... Mmm... this is exactly the reason why we had patches in CDK... to just comment out bits that were troublesome for applets... What about this option? A patch or an adapted version... or two separate classes using one interface... an AppletFileManager and a ProgramFileManager which would wrap around it with the extra DADML functionality? > > Otherwise, what would it require to use the JmolAppletProxy? Can you > > point me to piece of Jmol source code that uses it? > > The code in FileManager references the JmolAppletProxy. It allows the > unsigned applet to load arbitrary URLs ... by routing the request through > JmolAppletProxy.cgi ... which runs on the web server. Ack. E. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
