Wow, I like it! This isn't as crazy as it sounds. After just watching
the V8 talk from I/O, I've learned the JavaScript library is
implemented in JavaScript (preloaded in a heap snapshot).

The efficiency level they are hitting now makes this seem like a very
sensible approach, especially for Chrome, etc. If the WebSocket
standard ever materializes, it could be even better (and standards
based), and act as a last-resort fallback on all platforms.

I'm curious if it performs well enough for general use on Firefox? I
suspect it's quite a bit slower right now.

On Jun 5, 12:47 pm, Matt Mastracci <matt...@mastracci.com> wrote:
> On 5-Jun-09, at 10:08 AM, Piotr Jaroszyński wrote:
>
>
>
> > 2009/6/5 Matt Mastracci <matt...@mastracci.com>:
>
> >> While this subject is up...
>
> >> Has anyone considered writing the OOPHM client stub as a Java applet
> >> and using netscape.javascript.JSObject to deal with the JS  
> >> references?
>
> > Please no java applets. They only recently started working on 64bit
> > linux and I woudn't call them stable.
>
> Fair enough..  :)
>
> I haven't had much experience with applets on OSX, so I'm not sure  
> what the state is on this platform either.
>
> I've also been playing with a 100% Javascript version of the OOPHM  
> client stub as well, but it's been put on hold now that I've fixed the  
> bug in the binary component that was stopping me from instantiating it  
> from chrome:// documents.  It basically uses GWT and some XPCOM  
> bindings that I've generated for our product previously to implement  
> the client side of things.  It might be a good alternative to having a  
> binary component for FF, which is by far the browser that requires the  
> most cross-platform compilation.  It's no more than a proof-of-concept  
> right now, but if there's interest from others I can share the code  
> and/or work on completing it.  Since it's written using GWT, it's just  
> a matter of porting the current server-side BrowserChannel over.
>
> Matt.
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---

Reply via email to