caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Sébastien Dailly" <sebastien-ocaml@chimrod.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] js_of_ocaml with node
Date: Tue, 28 Apr 2015 09:08:21 +0200	[thread overview]
Message-ID: <5b9676217bdc376e005f6075f3808c69@chimrod.com> (raw)
In-Reply-To: <553EA747.8020105@gmx.net>

Le 2015-04-27 23:16, Helmut Brandl a écrit :

>> This a javascript limitation, not a js_of_ocaml one. I think (and 
>> hope) there is no such possibilities with standard javascript to 
>> create directories on the client fs. (and this would be a great 
>> security flaw if browsers would allow that).
> Maybe I have been misunderstood. I am not trying to run my code in a
> browser and access the client fs from the browers. My software package
> is compiled to bytecode of native using the ocam compiler. All I want
> to do is to create a javascript version and run it under nodejs (which
> runs on the client machine) to provide user which don't have an
> installed ocaml compiler suite on their machine to run my software
> package.
> 
> Note that nodejs has full access to the filesystem like any other
> program written in any programming language like C, ocaml, java,
> scala,...
> 

You'r right. I was only thinking of client side javascript.

Sorry for the noise.

-- 
Sébastien Dailly

  reply	other threads:[~2015-04-28  7:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 20:32 Helmut Brandl
2015-04-27 21:02 ` Sébastien Dailly
2015-04-27 21:16   ` Helmut Brandl
2015-04-28  7:08     ` Sébastien Dailly [this message]
2015-04-27 21:11 ` Daniel Bünzli
2015-04-27 22:03 ` Alain Frisch
2015-04-27 22:41   ` Daniel Bünzli
2015-04-28  7:53     ` Alain Frisch
2015-04-28  8:11       ` Alain Frisch
2015-04-28 11:17       ` Drup
2015-04-29 22:03         ` Helmut Brandl
2015-04-29 22:49           ` Mauricio Fernández

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=5b9676217bdc376e005f6075f3808c69@chimrod.com \
    --to=sebastien-ocaml@chimrod.com \
    --cc=caml-list@inria.fr \
    /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).