On 1 Oct 2011, at 15:28 , Stephan Beal wrote:
> On Sat, Oct 1, 2011 at 3:07 PM, Paul Ruizendaal wrote:
> > Maybe you could do some http-over-stdin/stdout, and speak json there. :)
>
> Isn't "fossil cgi" already doing that? A front-end could build the
> appropriate environment variables and for
On Sat, Oct 1, 2011 at 9:07 AM, Paul Ruizendaal wrote:
>
> > after every command fossil runs, exit() is called somewhere, which makes
> it difficult or impossible to chain commands together in the same app
> session.
>
> Why?
>
>
I built Fossil using the old-school unix design paradigm of a light
On 30 Sep 2011, at 16:28 , Jan Danielsson wrote:
> On 09/30/11 15:00, Tomek Kott wrote:
>>> On a semi-related note: Do the Windows binaries include SSL support?
>>>
>> I don't think so, because by default there's no openssl library installed
>> on win machines.
>
> If it is the case that it
On Sat, Oct 1, 2011 at 3:19 PM, Paul Ruizendaal wrote:
> There is something unsatisfying about the "mistake" solution, at least that
> is my feeling. Conceptually, there is a difference between not deleting
> history (which I think is a very valuable asset in fossil) and always
> showing full his
On Sat, Oct 1, 2011 at 3:07 PM, Paul Ruizendaal wrote:
> > Maybe you could do some http-over-stdin/stdout, and speak json there. :)
>
> Isn't "fossil cgi" already doing that? A front-end could build the
> appropriate environment variables and fork/exec "fossil cgi", feeding the
> post body to fos
There is something unsatisfying about the "mistake" solution, at least that is
my feeling. Conceptually, there is a difference between not deleting history
(which I think is a very valuable asset in fossil) and always showing full
history, rubbing mistakes in your face, especially when still lea
> Maybe you could do some http-over-stdin/stdout, and speak json there. :)
Isn't "fossil cgi" already doing that? A front-end could build the appropriate
environment variables and fork/exec "fossil cgi", feeding the post body to
fossil's stdin.
Actually, I was thinking that http/json was a more
2011/10/1 Lluís Batlle i Rossell
> Maybe you could do some http-over-stdin/stdout, and speak json there. :)
>
> I think of people wanting to write frontends to fossil.
>
i was just thinking about that while i was out shopping. It is, in
principal, possible, but fossil's heavy use of exit() as an
On Oct 1, 2011, at 9:24 , Ron Wilson wrote:
> On Fri, Sep 30, 2011 at 2:27 PM, Dmitry Chestnykh
> wrote:
>> The attacker cannot supply hash, he supplies password. To do timing attack,
>> the
>> attacker have to find a such string, for which the hash has a few bytes
>> changed.
>
> You and I se
I thought that was how fossil over ssh works already; on the far end fossil is
started with some undocumented private command that talks http over
stdin/stdout. you may well find your JSON work works transparently with that
mechanism too due to it being baked into the fossil http stack!
Sent fr
On Sat, Oct 01, 2011 at 11:23:32AM +0200, Stephan Beal wrote:
> 2011/10/1 Lluís Batlle i Rossell
>
> > But that's only a hack. The spawner will not know when the server will be
> > listening. And killing it, will not know if anyone else uses it and it is
> > working.
>
>
> i don't see any other
2011/10/1 Lluís Batlle i Rossell
> But that's only a hack. The spawner will not know when the server will be
> listening. And killing it, will not know if anyone else uses it and it is
> working.
i don't see any other way to do it unless/until fossil is split up into a
lib. The only entry point
On Sat, Oct 01, 2011 at 11:12:51AM +0200, Stephan Beal wrote:
> 2011/10/1 Lluís Batlle i Rossell
>
> > Sorry, not that I care much about JSON, but can json be used in a way that
> > a
> > program *spawns* fossil and talks to it using json, until it decides it's
> > enough and fossil stops?
> >
>
2011/10/1 Lluís Batlle i Rossell
> Sorry, not that I care much about JSON, but can json be used in a way that
> a
> program *spawns* fossil and talks to it using json, until it decides it's
> enough and fossil stops?
>
In theory, yes. It just has to start fossil server --port XYZ, send its
reque
On Sat, Oct 01, 2011 at 02:14:38AM +0200, Stephan Beal wrote:
> Hi, all!
>
> Another minor milestone: the 2nd proof-of-concept non-HTML client, this time
> in Java. It's fairly basic, and only supports synchronous operation, but
> it's a start.
Sorry, not that I care much about JSON, but can json
Hi, all,
i've started to implement /json/artifact, which is analogous to the /info,
/vinfo, etc. family of functions (but consolidated into one interface). It
is called like this:
/json/artifact/ID
or
/json/artifact?uuid=ID
where ID may be any artifact ID or tag (in which case it resolves to the
On Fri, Sep 30, 2011 at 2:27 PM, Dmitry Chestnykh
wrote:
> The attacker cannot supply hash, he supplies password. To do timing attack,
> the
> attacker have to find a such string, for which the hash has a few bytes
> changed.
You and I seem to be talking about different use cases, There are
sce
17 matches
Mail list logo
