P3
Following improvement suggestion had been made on the forum:
======
For HTTP/S issues, you may want to consider using Protocol Relative URLs (https://www.google.com/search?q=Protocol+Relative+URLs) in the javascript.
Example:
Instead of https://www.java.com/..... or http://www.java.com/....., use //www.java.com/..... for both.
That way people using dtjava.js don't have to do protocol checks and load different dtjava.js depending on whether the page is HTTP or HTTPS.
And this means you only need one version of dtjava.js instead of two (one for http and one for https).
=======
We also need to support file:// protocol but there are tricks that allow to do so too.
E.g. here is what was recommended for jquery:
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.js"></script>
<script>!window.jQuery && document.write(unescape('%3Cscript src="js/libs/jquery-1.4.2.js"%3E%3C/script%3E'))</script>
======
For HTTP/S issues, you may want to consider using Protocol Relative URLs (https://www.google.com/search?q=Protocol+Relative+URLs) in the javascript.
Example:
Instead of https://www.java.com/..... or http://www.java.com/....., use //www.java.com/..... for both.
That way people using dtjava.js don't have to do protocol checks and load different dtjava.js depending on whether the page is HTTP or HTTPS.
And this means you only need one version of dtjava.js instead of two (one for http and one for https).
=======
We also need to support file:// protocol but there are tricks that allow to do so too.
E.g. here is what was recommended for jquery:
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.js"></script>
<script>!window.jQuery && document.write(unescape('%3Cscript src="js/libs/jquery-1.4.2.js"%3E%3C/script%3E'))</script>