Currently, for Firefox users on Windows, a jinstall.exe is archived in the XPI package. When user clicks to install the XPI, its install.js launches the embedded jinstall.exe and passes to it the installmethod . There's 2 installmethod 's that stand for 2 different Firefox user's Java download traffics:
* jxpi: which stands for the traffic that goes directly to java.com.
* xpi: which stands for the traffic that is routed to java.com by Firefox PFS.
The XPI's jinstall.exe downloads/installs the IFTW.exe, and does a HTTP/1.1 POST to send the download/install info/status for marketing's java download monitoring purpose (java stat)
With XPI going away, the following changes are needed to continue support for Java download traffic monitoring (java stat) when users download java from java.com or via Firefox PFS:
* Stop building and staging XPI archives.
* To minimize change, continue to use the 2 installmethod names -- jxpi and xpi .
* Instead of the XPI archives, we will provide two EXEs, temporarily named jxpinstall.exe and xpinstall.exe to correspond to the two installmethod 's -- jxpi or xpi. Each EXE is an instance of deploy's generic jinstall.exe and requires no argument. Each EXE has its designated installmethod -- jxpi or xpi, built-in and is responsible for POST-ing metrics of its kind.
This CR has been approved by Core on 12/4/07.
Fix will be targeted to 6u5b02