Robert Wills wrote:
I've also thought that QHTML sounds like a good idea. The old version of QHTML used a java applet to communicate with the mozart server. I have wondered whether it would be possible to do this with javascript like in Ajax applications.
Well, AFAIK, JavaScript uses the now de facto JS object "XMLHTTPRequest" to hit the remote server, and given that this object has only a few simple methods, I doubt that it could set up an RPC protocol the way Java does.
AJAX can use any language an the remote server (and is not limited to getting just XML, either), so it doesn't really overcome the "Multiplicity of Languages" issue highlighted by PVR.
With AJAX, oz would simply return some XML or XHTML to the JS call, which would then have to process the data explicitly. I liked the Java applet idea, it seems realy flexible, but I haven't looked at the code yet.
So, for now, unless QHTML experiences some rennaisance (including Moz compatibility), things web-client-side remain firmly under the control of JS or, at a push, Java. Shame, really. So far, I've only been using IFrames for this kind of "partial page update" jiggery-pokery, something a little more elegant would be welcome.
_________________________________________________________________________________ mozart-users mailing list [email protected] http://www.mozart-oz.org/mailman/listinfo/mozart-users
