On Fri, Sep 16, 2011 at 5:07 AM, Ron Wilson ronw.m...@gmail.com wrote:
A simplification on templates would be a list of fields in the desired
order. Since most of the JSON responses would be lists of fields and
their values, this would achieve nearly all that templates could.
(True, some
On Tue, Sep 13, 2011 at 10:30 AM, Alaric Snell-Pym
alaric-ijh4firwi8dzyd0pdsz...@public.gmane.orgwrote:
by context, but it might be worth including JSON and human-HTML versions
of each URL, like so:
{
...stufff about a commit...
parents : {
hash of parent commit : { json :
On Thu, Sep 15, 2011 at 2:32 PM, fossil-m...@h-rd.org
fossil-m...@h-rd.orgwrote:
I think including links etc. gets baroque pretty fast, and different use
i think i would have used the word painful, but baroque is more colorful.
cases require different links. It may be better in the long
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
On Thu, Sep 15, 2011 at 8:32 AM, fossil-m...@h-rd.org
fossil-m...@h-rd.org wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/12/2011 05:07 PM, Stephan Beal wrote:
On Mon, Sep 12, 2011 at 5:50 PM, Richard Hipp d...@sqlite.org wrote:
Anchor tags in HTML are just one mechanism for providing hyperlinks. In
JSON, you could just as easily invent an alternative
On Tue, Sep 13, 2011 at 4:30 AM, Alaric Snell-Pym
ala...@snell-pym.org.uk wrote:
by context, but it might be worth including JSON and human-HTML versions
of each URL, like so:
{
...stufff about a commit...
parents : {
hash of parent commit : { json : http://..json;, html
:
On Mon, Sep 12, 2011 at 6:44 PM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Sep 13, 2011 at 12:35 AM, Ron Wilson ronw.m...@gmail.com wrote:
I would add LinkDescription:description to that, or possibly
LinkDescription:URL, but usually the description would be short
That actually
On Tue, Sep 13, 2011 at 5:35 PM, Ron Wilson ronw.m...@gmail.com wrote:
Raw delivery of wiki pages is an issue of its own. I have not yet
looked into that, as I have been able to make do with surounding the
wiki content with nowiki ... /nowiki (which I mentioned in a post
some while back).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/13/2011 04:24 PM, Ron Wilson wrote:
On Tue, Sep 13, 2011 at 4:30 AM, Alaric Snell-Pym
ala...@snell-pym.org.uk wrote:
by context, but it might be worth including JSON and human-HTML versions
of each URL, like so:
{
...stufff about a
On Sun, Sep 11, 2011 at 12:55 AM, Stephan Beal sgb...@googlemail.comwrote:
This question is primarily aimed at Richard, but anyone who's got some
insight or opinions is of course free to chime in...
As i understand it, the primary intention behind requiring the anonymous
user login is to
On Mon, Sep 12, 2011 at 1:26 PM, Richard Hipp d...@sqlite.org wrote:
There should be links. Without them, the interface is not fully RESTful.
See http://martinfowler.com/articles/richardsonMaturityModel.html for
further information. A key idea behind REST is that an application can be
given
On Mon, Sep 12, 2011 at 11:33 AM, Stephan Beal sgb...@googlemail.comwrote:
On Mon, Sep 12, 2011 at 1:26 PM, Richard Hipp d...@sqlite.org wrote:
There should be links. Without them, the interface is not fully RESTful.
See http://martinfowler.com/articles/richardsonMaturityModel.html for
On Mon, Sep 12, 2011 at 5:50 PM, Richard Hipp d...@sqlite.org wrote:
Anchor tags in HTML are just one mechanism for providing hyperlinks. In
JSON, you could just as easily invent an alternative mechanism. Perhaps an
object:
{
LinkType: Next,
URI:
On Mon, Sep 12, 2011 at 11:50 AM, Richard Hipp d...@sqlite.org wrote:
Anchor tags in HTML are just one mechanism for providing hyperlinks. In
JSON, you could just as easily invent an alternative mechanism. Perhaps an
object:
{
LinkType: Next,
URI:
On Tue, Sep 13, 2011 at 12:35 AM, Ron Wilson ronw.m...@gmail.com wrote:
I would add LinkDescription:description to that, or possibly
LinkDescription:URL, but usually the description would be short
enough to not worry about. Also, it would not, for example, be
unreasonable for the description
On 11 Sep 2011, at 05:55, Stephan Beal wrote:
In a JSON context, link-following is not an issue. There are no links, as
such, in JSON docs - though individual JSON strings might incidentally
contain HTML link strings, bots don't generically try to extract HTML text
from JSON. Doing
Right now for the fossil repository itself, I can read write some stuff, but
I cannot read everything. For example, I cannot read the complete list of
users. So the sentence As far as i can see so far, the only ops which _need_
to be authenticated (for purposes of a JSON interface) are
On Sun, Sep 11, 2011 at 3:50 PM, Weber, Martin S martin.we...@nist.govwrote:
Right now for the fossil repository itself, I can read write some stuff,
but I cannot read everything. For example, I cannot read the complete list
of users.
You're right. The only multi-user repo i work on is
This question is primarily aimed at Richard, but anyone who's got some
insight or opinions is of course free to chime in...
As i understand it, the primary intention behind requiring the anonymous
user login is to keep spiders from crawling the whole repo history, and the
distinction between the
20 matches
Mail list logo
