On Fri, Sep 9, 2011 at 7:38 AM, Martin S. Weber wrote:
> are talking about REST and JSON, but you really, really mean JSON
> over HTTP. What I'm trying to say is that you seem more concerned
>
Yes, i am very possibly abusing some terminology. :/ Feel free to set me
straight.
> preference of us
On Fri, Sep 9, 2011 at 7:31 AM, Steve Bennett wrote:
> $ ./configure CFLAGS="-Wall -Werror -g -O2"
> $ make
>
Works like a charm - thanks :).
--
- stephan beal
http://wanderinghorse.net/home/stephan/
___
fossil-users mailing list
fossil-users@list
On 09/09/2011, at 12:13 PM, Stephan Beal wrote:
> Hi, all!
>
> Is there a way, using the new config process, to enable -Wall and -Werror? i
> find it painful building without them.
>
> --
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> _
On Fri, Sep 9, 2011 at 4:58 AM, Stephan Beal wrote:
> It's not much, but it's a start:
>
i've got it up on my hoster:
http://fossil.wanderinghorse.net/repos/fossil-sgb/index.cgi/json/HAI
(HAI is an alias for "version", by the way)
For the current (long) list of TODOs, see:
https://docs.googl
On Fri, Sep 9, 2011 at 5:24 AM, Richard Hipp wrote:
> I'm certainly no REST expert, but this seems very unRESTful to me...
>
i was just reading through the wikipedia page on it and indeed they
explicitly count stateless as a core property (which i wasn't aware of).
Well, the capability is there
On Fri, Sep 9, 2011 at 5:03 AM, Stephan Beal wrote:
> Hi, all!
>
> Would this be even marginally useful: persistent sessions in fossil (i.e.
> cross-request data tied to a given login)?
>
> The JSON bits i'm using include this support and it can use arbitrary
> storage back-ends via a generic int
Hi, all!
Would this be even marginally useful: persistent sessions in fossil (i.e.
cross-request data tied to a given login)?
The JSON bits i'm using include this support and it can use arbitrary
storage back-ends via a generic interface. It would take all of about 20 or
30 minutes to put togethe
It's not much, but it's a start:
Here's the code (not counting 10 or 12 lines of infrastructure-level code):
/*
** WEBPAGE: /json
**
*/
void json_page_top(void){
Blob buf = empty_blob;
cson_value * json = NULL;
cgi_set_content_type( cson_cgi_guess_content_type(&g.csonCgi) );
json = cson_c
Hi, all!
Is there a way, using the new config process, to enable -Wall and -Werror? i
find it painful building without them.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
h
On Thu, Sep 8, 2011 at 10:27 PM, Stephan Beal wrote:
> i recommend JSON mainly for portability. It can be generated (with some
> limitations) even from shell scripts and posted via wget or curl.
> Form-encoding is more expensive and (with JSON) unnecessary. That said, i
> have code in place (in a
On Thu, Sep 8, 2011 at 11:05 PM, Jos Groot Lipman wrote:
> **
> A well designed JSON-interface would certainly have made my experiment
> easier.
>
Then keep the ideas coming :).
>
> One thought: when the interface would rely on GET/POST it might create
> cross-
>
domain problems when used from
A JSON/REST interface sounds very promising.
A few weeks ago I was playing around and tried creating a client-side
file-browser treeview in HTML.
What I ended up doing was getting the raw artifact (/raw/) and parsing it
clientside. Not exactly perfect so I dropped it.
A well designed JSON-inter
On Thu, Sep 8, 2011 at 10:27 PM, Stephan Beal wrote:
> week about that, actually, and we discussed a few implementation
> differences.) The current code (called cson) is Public Domain, so there's no
> licensing constraint. See: http://whiki.wanderinghorse.net/wikis/cson/
>
Actually... the underl
On Thu, Sep 8, 2011 at 10:11 PM, Martin S. Weber wrote:
> On 09/08/11 16:01, Stephan Beal wrote:
>
>> 1) A split between library and app. i.e. libfossil vs. the fossil
>> server/cgi/shell app(s)
>>
>
> I couldn't agree more. One of my goals (luckily no milestone I'll ever be
> evaluated against) i
On Thu, Sep 8, 2011 at 10:08 PM, Ingo Koch wrote:
> Take a look at
>
> http://arnebachmann.pytalhost.de/pdf/integrated-version-control-with-fossil-scm.pdf
>
> Hope that helps
>
Absolutely! Every slide i don't have to type in myself helps :).
Vielen Dank und schoenen Gruess aus Muenchen!
--
--
On 09/08/11 16:01, Stephan Beal wrote:
Hi, all!
Management Summary: if you are _at all_ interested in seeing a JSON
REST-style interface added to fossil, please continue reading. If not,
don't bother!
Since you've read this far, we'll go ahead and continue...
Earlier this week i was awarded th
On 08.09.2011 11:41, Stephan Beal wrote:
> Hi, all,
>
> i remember at least one or two list members mentioning (in the relatively far
> past) doing presentations on Fossil. This question is for them...
>
> The company i work for allows us to propose so-called R&D topics, where we get
> a few days o
Hi, all!
Management Summary: if you are _at all_ interested in seeing a JSON
REST-style interface added to fossil, please continue reading. If not, don't
bother!
Since you've read this far, we'll go ahead and continue...
Earlier this week i was awarded the great pleasure of sitting down with DRH
Hi, all,
i remember at least one or two list members mentioning (in the relatively
far past) doing presentations on Fossil. This question is for them...
The company i work for allows us to propose so-called R&D topics, where we
get a few days of budget to go research a topic (typically a new/up-c
19 matches
Mail list logo
