Yes, that is intentional. The threading is now handled inside the library. You only need to be concerned with the API methods exposed by edu.stanford.ejalbert.BrowserLauncher. See http://browserlaunch2.sourceforge.net/docs.shtml#apinotes.
Let me know if you need more information or if the documentation is insufficient.
Jeff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems that in the 1.0 release you changed the BrowserLauncherRunner not to be public.
Is that intentional?
Thanks,
Guy.
Hi Guy,
Yes, that is intentional. The threading is now handled inside the library. You only need to be concerned with the API methods exposed by edu.stanford.ejalbert.BrowserLauncher. See http://browserlaunch2.sourceforge.net/docs.shtml#apinotes.
Let me know if you need more information or if the documentation is insufficient.
Jeff