Robert Hanson wrote: > I have tentatively modified Jmol to make > > load "/xxx/xxx" > > for the application and the SIGNED applet default to > > load "file:/xxx/xxx" > > and for the UNSIGNED applet default to > > load "http://whatever.server/xxx/xxx"; > > when the applet is on a server or > > load "file:/xxx/xxx" > > when it is local. > > Rationale: > > --The remote unsigned applet couldn't load file:/xxx anyway. > --No change then for unsigned applet behavior relative to 11.4 > --Unlikely anyone has been using the signed applet to read files via root of > webserver > > I'm not totally happy with this, because it allows two different behaviors > between the signed and unsigned applets, but I think it will let us proceed > with 11.6, since it represents no change in the unsigned applet, and almost > certainly the desired behavior with the signed applet and application. > > Comments requested. > With regard to backward compatibility this seems to be a good way to go. But if there are no others out there using server absolute paths beside me I could also live with a different solution. (e.g.: a switch enabling server absolute paths.)
Q: What happens if the user doesn't accept the certificate? Could the applet detect this? (Currently there still is shown the "Jmol_S" logo although it hasn't all the capabilities.) Regards, Rolf ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
