W3C home > Mailing lists > Public > spec-prod@w3.org > April to June 2013

Re: Specref API

From: Tobie Langel <tobie@w3.org>
Date: Tue, 25 Jun 2013 12:09:35 +0200
To: Robin Berjon <robin@w3.org>
Cc: spec-prod@w3.org, Marcos Caceres <w3c@marcosc.com>
Message-ID: <6EA9FEEA2A14413E8805F4A6A5CC4966@w3.org>
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.

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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:18 UTC