Scott, Is there a reason this fix couldn't be folded in to the webstart deploy process rather than be a separate program Mac users have to run (and then run again whenever they update Java).
We've talked about modifying the webstart deploy process to have a minimal initial set of jars downloaded and run first providing useful information to the user about both what is happening and is about to happen. I'm going to call this set of jars and the functionality they provide "Part1". Obviously this division into parts is part of the functionality you are working on for the webstart-jar-proxy server. What about adding the ability to check and even fix if needed the jar-differencing bug on a Mac as part of this same. Could we refuse to provide the Part1 jars in jar-difference forms to Macs? If so then we know that even Mac's without the webstart fix would be able to download these jars. Perhaps if the computer is a Mac then we should provide just the jar for checking and fixing the webstart bug as a Part0 section in the jnlp. The idea is that this jar is always run first on a Mac before any other jars are loaded. Then the jars that might need to be updated in the real Part1 cold use jar-differencing. I assume that if the problem is found and fixed then the whole jnlp process might need to be started again -- if this can't be done easily for the user then I suppose the webstart-fixer could end with a dialog telling the user what had been fixed and ask them to close the dialog they are looking at and run the software again by clicking on the webstart link in the html they had just been viewing originally. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
