On Dec 7, 6:48 pm, "Ted Kosan" <[EMAIL PROTECTED]> wrote: > Carl wrote: > > If the applet uses java.net.HTTPUrlConnection to talk to the server > > from Java, it doesn't have to log in separately... the cookies from > > the browser's login are automatically used by the Java > > communications. At least, it works for me, and this document > > indicates that it should be portable (unless we care about Netscape > > 4 :): > > http://java.sun.com/j2se/1.4.2/docs/guide/plugin/developer_guide/cookie_support.html > > I also experimented with using the AsyncHttpRequest class: > > http://swinglabs.org/hudson/job/SwingX-WS%20Continuous%20Build/javadoc/org/jdesktop/http/async/AsyncHttpRequest.html > > Currently, however, the applet is being served from a different server > than the SAGE server it is communicating with. Doesn't this prevent > it from contacting the SAGE server directly unless it is signed?
I was using an applet that was served by the Sage server. If you have a file $SAGE_ROOT/local/java/foo.jar, then it is available through the Sage server as https://localhost:8000/java/foo.jar (assuming default settings). Carl --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
