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": "http://www.fossil-scm.org/fossil/json/timeline?first=12345
> "
> }
>
That looks good.
@Anyone who's got ideas for how to best represent stuff like that, feel free
to chime in. This doesn't just apply to the timeline, but potentially to any
page which presents "detail links" (as opposed to the nav links in the page
header and whatnot).
We should probably come with with a common set of data types/structures for
re-use throughout the API, e.g. hyperlinks, user information, wiki pages,
etc. So far i've just been ad-hoc'ing it and there haven't yet been any
"shared" types/structures except timestamps (for which i use Unix Epoch GMT,
for portability). There eventually will be a need for several common/shared
structures, though.
I'm not saying this is necessarily the best way to do things. But it is the
> RESTful way to do things.
>
i'm not experienced enough with apps like this to suggest any best
practices, so keep the ideas coming. :)
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
