Tuesday, April 8th, 2008
I started a new series of posts on Web Archeology where I look back at old Web tech to maybe divine some inspiration from the future. I am re-posting from my original blog
Even since Ben and I looked at the notes for the first version of Mozilla that supported XMLHttpRequest, which suddenly took the technology from â€œSome ActiveX for IEâ€ to â€œAjaxâ€, I have been interested in hidden technologies that maybe never made it. In those notes for that release we saw no mention of XMLHttpRelease, but technology such as FIXptr was prominently mentioned.
Also, something interesting about Ajax is exactly the fact that the technology was available since 1997, but didnâ€™t make it big until many more Dilbert calendars later.
This points to the fact that there may be some hidden gems in the past that could also be resurrected in the now! As I look back in time, I thought I would talk about any that interest me in some way. Hence, the Web Archeology set of postings. If there is a technology that I am missing, please let me know!
What if the Java developers could get in on the browser action and develop rich plugins for Mozilla? This is where the Java Pluglet API comes in. It allows you to do just that, mimicking the C++ side of the house:
It was a conscious design decision to have the Pluglet API resemble its C++ counterpart as much as possible, while being able to reflect all of its functionality to Java, so that Plug-in writers will not have to learn yet another API. This concern, in our opinion, outweighed other alternatives which offered a cleaner, more Java-like look. Support for other Plug-in APIs can be easily added by contributing adaptors.
How you register the pluglet is via mime types. You could create
application/wicked-cool and when that comes back from the server, Mozilla will say â€œhmm, I donâ€™t understand this mime type, Pluglet Engine do you?â€
At a high level the idea of writing extensions in Java makes total sense to me. It is obviously cross platform, but still low level enough, with a huge library set to get a lot done.
Isnâ€™t this dead?
If you squint a little, you see an interesting plugin path for the browser. I often say that I would love for Gears to be made using Java instead of C++!
Dimitri Glazkov pointed to the custom handler support that has been specified in HTML 5, and Ray Cromwell linked to his GWT 1.5 posting as a way to extend the browser using Java.
Posted by Dion Almaer at 8:39 am