help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sharing scripts


From: Sergei Steshenko
Subject: Re: Sharing scripts
Date: Sat, 20 Mar 2010 05:55:11 -0700 (PDT)


--- On Fri, 3/19/10, Søren Hauberg <address@hidden> wrote:

> From: Søren Hauberg <address@hidden>
> Subject: Re: Sharing scripts
> To: "MathCloud" <address@hidden>
> Cc: address@hidden
> Date: Friday, March 19, 2010, 7:53 PM
> Hi and sorry about the late reply
> (I've been vacationing a bit lately so
> I'm still catching up on e-mail)
> 
> søn, 14 03 2010 kl. 04:15 -0700, skrev MathCloud:
> > I am not sure what you mean by making the source code
> available? You mean
> > the code that implements the web interface? If so,
> that is not my intention
> > at this point.
> 
> Yes this is what I mean. To me, this is essential for
> several reasons.
> The two most important reasons are
> 
>       * I use Octave for scientific purposes
> and I don't believe I can
>         use a piece of software as part
> of my work unless I can actually
>         look under the hood (no
> black-boxes in science).
>       * From time to time I have to work
> with confidential data that I
>         would never upload to some
> arbitrary web server on the net. I
>         would need to have complete
> control of the server.
> 
> Anyway, I wish you the best of luck with your service and I
> hope you
> will decide to release the code at some point.
> 
> Cheers,
> Søren
> 

Søren,

at the moment you work with somebody esle's server you can't be sure what
it is doing even if you think you have the server side source code.

I.e. you may be given the modified server side source code, and looking at
it and comparing the server behavior with code you might come to the conclusion 
that the server is doing what it is prescribed by the server
side source code.

In reality, however, you might be given edited source code with pieces
backing up all submitted scripts and their input/output data omitted.

Regards,
  Sergei.


      



reply via email to

[Prev in Thread] Current Thread [Next in Thread]