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 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.
Yes, I think t would be a simple way to get a lot of flexibility. 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 fields do have complex values, but a field list should be simple to implement and would be a good next step) _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
