Re: Specref API

On Tuesday, June 25, 2013 at 11:58 AM, Robin Berjon wrote:
> Hi Tobie,
> 
> On 25/06/2013 11:43 , Tobie Langel wrote:
> > I need to access more data than what the Specref API currently
> > provides (this will include things like test suite URL, "deliveredBy"
> > property (link to the WG that produces the spec, etc.).
> > 
> > Question is: should I create another end-point for this extra-data
> > and leave /bibref untouched or should I add this to /bibref?
> 
> The only thing that I care about from the ReSpec point of view is 
> performance. If you're only adding a few fields, it probably doesn't 
> matter, but if you're adding enough that the output might start being 
> noticeably slower to load and parse, then I'd rather the API that ReSpec 
> uses stayed lean and mean.

Most requests are clocking well above a single packet, so I don't think even doubling the size of the output would have a significant perf impact.

--tobie

Received on Tuesday, 25 June 2013 10:09:44 UTC