Dev Chat on Open JVM Integration Postponed
Thursday December 9th, 1999
Our planned developer chat, a Q&A on OJI with Ed Burns, has been postponed due to problems with network connections on the east coast. If you're interested in knowing more about OJI and its progress, be sure to stop by Mozilla.org's OJI pages. We will be posting a new chat schedule soon, and this chat will be rescheduled then.
Also, our XPCOM chat with Suresh Duddi and Scott Collins from last week has been rescheduled for next Friday, December 17th, at 3:00pm PST.
#1 Sounds interesting
Thursday December 9th, 1999 3:44 PM
Too bad I'm going to miss it. If anyone's listening, please put the log of it on MozillaZine. Thanks.
#2 One more thing...
Thursday December 9th, 1999 3:50 PM
Someone be sure to ask him what the status of Open JVM Intergration for Linux is, and what JVM are available (going to be available) for Linux Mozilla. Thanks again.
#3 JVM / Linux
Friday December 10th, 1999 12:54 AM
I'm not going to be able to attend, either, but please ask whether current JREs for Linux (such as Blackdown, IBM) can be used with Mozilla and if it will be possible to use non-Java VMs through the OJI and, if so, how language detection will be done.
Friday December 10th, 1999 5:58 AM
1) at work i live behind a strict firewall with no IRC access. you might want to look into supporting the javasoft developer's connection chat applet which works over HTTP.
3) will mozilla augment the java security system in any way? e.g. the management of certs, the management of permissions, etc?
4) how will mozilla's cache be integrated with java? will the user get some control over the caching of .class and .jar files? will the provider of .class and .jar files have a way to request specific cache behavior?
#5 Re: thoughts
Friday December 10th, 1999 8:20 AM
#6 Re: Re: thoughts
Friday December 10th, 1999 8:33 AM
#7 Re: Re: Re: thoughts
Friday December 10th, 1999 4:09 PM
I guess it depends on the JVM and JIT. Not all OSes support for Java is that good.
#8 Rhino speed
Saturday December 11th, 1999 4:21 AM
That's because it has two modes. In the interpreted mode, it's *WAY* slower than the C/C++ version of the engine. In compiled mode, where everything is actually Java when it runs, it's somewhat faster than the C/C++ counterpart. I don't have any numbers on how long compiling takes etc.. Using compiled mode in a browsing environment is probably not an option.