P2
dtfx.js should generate applet tag as soon as possible for most of cases.
E.g. liveconnect is expensive but dtfx can hardcode latest (popular) version (or two) of JRE available and quickly check mime types for their availability.
Majority of users have few versions of JRE installed and this will likely reduce startup time for them.
If fast check fails to find known good jre then we can revert to current procedure (or improve it).
One other thing is that we should not require deployJava.js unless it is needed.
I.e. if fast check helps to find appropriate JRE then we do not need to insert tag for deployJava into html.
We only need to do this if fast check failed (and may be even more sophisticated checks fail too) but in that case this will not be fast start anyway.
See also RT-5240 that is expected to be fixed as part of this bug.
E.g. liveconnect is expensive but dtfx can hardcode latest (popular) version (or two) of JRE available and quickly check mime types for their availability.
Majority of users have few versions of JRE installed and this will likely reduce startup time for them.
If fast check fails to find known good jre then we can revert to current procedure (or improve it).
One other thing is that we should not require deployJava.js unless it is needed.
I.e. if fast check helps to find appropriate JRE then we do not need to insert tag for deployJava into html.
We only need to do this if fast check failed (and may be even more sophisticated checks fail too) but in that case this will not be fast start anyway.
See also RT-5240 that is expected to be fixed as part of this bug.