I haven't touched this aspect in a month or two, but isn't there an option to indicate whether or not to download the latest version, and also an option to prompt the user to download the latest?
--Ryan On Thu, Oct 1, 2009 at 4:09 PM, Joshua Marinacci <jos...@marinacci.org>wrote: > > You can tell if draggable applets and 6u10 are available using the > javascript functions in the Java Deployment Toolkit (deploy.js and > dtfx.js). > > If the user doesn't have the supported configuration they can still > run the applet, they just won't get the drag ability and will always > have to return to your website. > > - Josh > > On Oct 1, 2009, at 12:40 PM, Jess Holle wrote: > > > Joshua Marinacci wrote: > >> > >>> The fact that when you launch a Java Web Start application from the > >>> browser there is no hand-off of the current cookie set, etc, is > >>> problematic -- and has led to double authentication in various use > >>> cases > >>> for us. > >>> > >>> I suppose restructuring as a draggable applet would avoid that? > >>> > >> Yes. > >> > > So I suppose I need to auto-detect if Java 6 Update 10 or higher is > > available and, if not, fall back to a normal non-applet JNLP approach? > > > > [Questions like this have left me not using this neat feature -- as > > I cannot guarantee Java 6 Update 10 or higher, nor can I give up on > > those without it.] > > > > -- > > Jess Holle > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
