Re: [fossil-users] authentication in JSON: anonymous vs. guest user
Hi, the template approach in my last post could also be used for the wsdl stuff mentioned in another thread about json. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] authentication in JSON: anonymous vs. guest user
On Tue, Sep 13, 2011 at 10:30 AM, Alaric Snell-Pym
wrote:
by context, but it might be worth including JSON and human-HTML versions
of each URL, like so:
{
...stufff about a commit...
"parents" : {
"" : { "json" : "http://..json";, "html"
: "http://...html"; },
"" : { "json" : "http://..json";, "html"
: "http://...html"; }
}
}
I think including links etc. gets baroque pretty fast, and different
use cases require different links. It may be better in the long run
to simply add a kind of template mechanism to the server. This is
explained on p. 297 in "Effective Tcl/Tk Programming" by M. Harrison
and M. McLennan. Basically the client sends a request giving a
template and the data it wants. This allows each client to get fossil
data in the format the client needs, with just the data fields it
needs. So a client could request just the title of a ticket, or just
the contents.
http://.../ticket.json&{"title"+:+$title} as an example
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Draft doc for JSON/REST Fossil interface
Great idea! Please consider that when using cgi a complete REST over http style interface is not supported: cgi defines only http GET and POST DELETE and PUT are not in the cgi spec and handled differently by different httpd's. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil idea: vendor branches, subprojects and foreign code libs
Hi, recently there were a few discussions on how fossil handles (or not handles) subprojects and getting external code libraries into fossil. Maybe looking at PRCS ( http://prcs.sourceforge.net/ , not maintained anymore since 2003/2004), on "old" revision control systems is interesting. It shares some features/ideas with fossil, but with a different emphasis. In the documentation (available from the above site) there are two sections which may be interesting for fossil: - Subprojects - Importing Project Versions In part PRCS relies on an editable control file in the repository such that subprojects can be checked out within parent projects. hope this is interesting. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
