From: "Mattias Waldau" <mattias.waldau@abc.se>
To: "Dave Berry" <dave@kal.com>,
"John Max Skaller" <skaller@ozemail.com.au>,
"Markus Mottl" <mottl@miss.wu-wien.ac.at>
Cc: "OCAML" <caml-list@inria.fr>
Subject: XML, HTTP, SOAP (was RE: JIT-compilation for OCaml?)
Date: Wed, 10 Jan 2001 10:12:15 +0100 [thread overview]
Message-ID: <HDEEKOMJILGEIHIMAPCDEEFBDNAA.mattias.waldau@abc.se> (raw)
In-Reply-To: <3145774E67D8D111BE6E00C0DF418B663A7C76@nt.kal.com>
> Dave Berry wrote
> 3. Web programs require interfacing to web browsers. Perhaps someone
> could add the OCaml VM to Mozilla?
I don't believe we need Ocaml as a VM, I am not even sure that Java will
exist as a VM in the future. Most advanced WEB-clients today are coded using
Javascript (or sometimes VBscript).
Thin clients is a good approach! By implementing the Ocaml-program as a
multithreaded HTTP-server which exports its functions using XML or SOAP
(typed rpc over HTTP encoded by XML), very advanced interfaces can be done
easily.
The client consists of a Javascript program, or stylesheets or some of the
newer XML-technologies.
If you restrict yourselves to modern browser (ie 5, netscape 6), there are
good nice way reducing the amount of javascript coding. One example is HTC.
These kinds of interfaces can both be used locally (http://localhost) or
over the internet. Performance is very good locally, I know from practical
experience.
Creating a table using HTML is very often much easier than creating a user
interface with a listbox with columns and filling it.
/mattias
next prev parent reply other threads:[~2001-01-10 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 17:09 JIT-compilation for OCaml? Dave Berry
2001-01-10 9:12 ` Mattias Waldau [this message]
2001-01-11 6:38 ` John Max Skaller
2001-01-11 12:42 XML, HTTP, SOAP (was RE: JIT-compilation for OCaml?) Dave Berry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=HDEEKOMJILGEIHIMAPCDEEFBDNAA.mattias.waldau@abc.se \
--to=mattias.waldau@abc.se \
--cc=caml-list@inria.fr \
--cc=dave@kal.com \
--cc=mottl@miss.wu-wien.ac.at \
--cc=skaller@ozemail.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).