>> * We will have to make some modifications to the present code to get >> it >> to work with the JmolApplet. The applet security model will only allow >> the JmolApplet to retrieve URLs from its home server. Therefore, all >> URLs which are fetched by the unsigned JmolApplet must be routed >> through the JmolAppletProxy. >> * It isn't clear to me how much of the 'dadml' intelligence we want >> to >> put in the JmolAppletProxy and how much we want to leave in the >> JmolApplet code itself. That is, we could leave all the 'intelligence' >> in the JmolApplet. Or, we could encode this in the JmolAppletProxy >> that runs on the web server. > > The DADML library is only 30k-ish...
The problem is not size. The problem is that the security manager prevents an applet from retrieving URLs from another web server. > But I do not think this is something we need for the applet anyway: If it does not belong in the applet then we should move it out of the viewer code. > 1. the applet is right with the website... so I think there is no need > to resolve things... It might be right on your website, but it is not on other websites. I was hoping that we could use something like this as a general-purpose mechanism for retrieving data from web-accessible databases. Miguel ------------------------------------------------------- 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
