From: ben kuin <benkuin@gmail.com>
To: Richard Jones <rich@annexia.org>, caml-list@inria.fr
Subject: Re: [Caml-list] web server interface for Ocaml ( like rack, wsgi, ...)?
Date: Tue, 21 Sep 2010 09:50:36 +0200 [thread overview]
Message-ID: <AANLkTi=KxH6A6P4MZKZ0GbSAgtxBJy_Bskj3nVAQ0ph3@mail.gmail.com> (raw)
In-Reply-To: <20100919103258.GA14826@annexia.org>
> what's wrong with simply proxying the HTTP connections through your favorite webserver to the backend ocsigen/ocamlnet server?
Nothing per se. I've tried so set something up with ocsigen, but I had
to give up. There seems to be a certain philosophy behind it how you
should writing web apps.
But I just wanted to do something:
- small ( one page app )
- quick and dirty ( no big setup upfront, no compilation)
- deployment, by dropping a (ocaml script) into a webroot, not matter
what webserver is running
- permissive license ( mit, ...)
~~~~ from wikipedia ~~~~
require 'rack'
app = Rack::Builder.app do
lambda do |env|
body = "Hello, World!"
[200, {"Content-Type" => "text/plain", "Content-Length" =>
body.length.to_s}, [body]]
end
end
~~~~~~~~~~~~~~~~~~~~
On Sun, Sep 19, 2010 at 12:32 PM, Richard Jones <rich@annexia.org> wrote:
> On Thu, Sep 16, 2010 at 10:29:23AM -0700, Jake Donham wrote:
>> On Thu, Sep 16, 2010 at 4:05 AM, ben kuin <benkuin@gmail.com> wrote:
>> > Is there a web server interface / adapter for ocaml that abstracts
>> > your application from the various web server implementations?
>>
>> There is no OCaml equivalent to rack / wsgi. It would be nice to have
>> something like this; the existing web frameworks (e.g. Ocamlnet and
>> Ocsigen as another poster mentioned) implement the whole stack, but it
>> would be nice to be able to mix and match (e.g. run Ocsigen's Eliom
>> applications in Ocamlnet's Netplex server). Part of the difficulty is
>> that there are different approaches to concurrency/asynchrony (Lwt for
>> Ocsigen, Equeue for netplex). My impression is that rack / wsgi punt
>> on this issue, and assume threading. But an OCaml equivalent could
>> possibly offer both a concurrent/asynchronous and a direct-style
>> interface.
>
> Maybe I'm missing the point, but what's wrong with simply proxying the
> HTTP connections through your favorite webserver to the backend
> ocsigen/ocamlnet server?
>
> Rich.
>
> --
> Richard Jones
> Red Hat
>
next prev parent reply other threads:[~2010-09-21 7:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 11:05 ben kuin
2010-09-16 16:04 ` [Caml-list] " Michael Ekstrand
2010-09-16 17:29 ` Jake Donham
2010-09-16 19:00 ` Paolo Donadeo
2010-09-16 22:04 ` Dario Teixeira
2010-09-16 22:27 ` Michael Ekstrand
2010-09-16 23:55 ` Vincent Balat
2010-09-17 8:08 ` Paolo Donadeo
2010-09-17 8:03 ` Paolo Donadeo
2010-09-17 7:59 ` Paolo Donadeo
2010-09-17 8:57 ` Stéphane Glondu
2010-09-19 10:32 ` Richard Jones
2010-09-21 7:50 ` ben kuin [this message]
2010-09-21 19:20 ` Richard Jones
2010-09-21 19:46 ` Gerd Stolpmann
2010-09-21 19:58 ` Martin Jambon
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='AANLkTi=KxH6A6P4MZKZ0GbSAgtxBJy_Bskj3nVAQ0ph3@mail.gmail.com' \
--to=benkuin@gmail.com \
--cc=caml-list@inria.fr \
--cc=rich@annexia.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).