caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Nicolas Cannasse <ncannasse@motion-twin.com>
To: David MENTRE <dmentre@linux-france.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Small comparison of OCaml web frameworks
Date: Wed, 12 Jul 2006 09:37:48 +0200	[thread overview]
Message-ID: <44B4A6CC.6070607@motion-twin.com> (raw)
In-Reply-To: <87zmffc1l3.fsf@linux-france.org>

> Hello,
> 
> I've started a short comparison of OCaml web frameworks for WDialog,
> Ex-Nunc, Ocsigen and mod_caml:
>   http://www.demexp.org/en/doku.php?id=web_client_development_framework#comparison_of_ocaml_frameworks
> 
> This page is a Wiki. Feel free to fix any error or omission you might
> see (please add a meaningful comment in that case), as I have not tested
> each framework (except WDialog).
> 
> I'm also interested into other criteria of comparison you might see
> interesting.
> 
> Best wishes,
> david

Hi David,

I added both haXe (http://haxe.org) and Neko (http://nekovm.org) to the
list of your web frameworks.

Since the haXe compiler is written in OCaml, that might interest some
people on this list as well. haXe is an high-level OO language with a
modern type system (type inference, enums, ML polymorphism). It targets
three platforms :
  - it has a Javascript/AJAX code generator so you can use it to code
the client side of your website.
  - it has a Neko code generator that can be used with NekoVM to write
the server side of your website : NekoVM is a small embeddable VM with a
"mod" for Apache.
  - it has a Flash/SWF generator so you can use haXe to develop Flash
RIA and other applications.

Nicolas


      reply	other threads:[~2006-07-12  7:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 20:45 David MENTRE
2006-07-12  7:37 ` Nicolas Cannasse [this message]

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=44B4A6CC.6070607@motion-twin.com \
    --to=ncannasse@motion-twin.com \
    --cc=caml-list@inria.fr \
    --cc=dmentre@linux-france.org \
    /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).