W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2014

Re: Thinking about cross references and ReSpec

From: Tobie Langel <tobie.langel@gmail.com>
Date: Thu, 2 Oct 2014 14:24:13 +0200
Message-ID: <CAMK=o4fBxgEcdNR7GT-zheWrTgUWoz0rMNyU8fV8cK7aRYKfuA@mail.gmail.com>
To: Shane McCarron <shane@aptest.com>
Cc: Robin Berjon <robin@w3.org>, "spec-prod@w3.org Prod" <spec-prod@w3.org>
On Thu, Oct 2, 2014 at 2:18 PM, Shane McCarron <shane@aptest.com> wrote:

> On Thu, Oct 2, 2014 at 7:15 AM, Tobie Langel <tobie.langel@gmail.com>
> wrote:
>
>> On Thu, Oct 2, 2014 at 1:49 PM, Shane McCarron <shane@aptest.com> wrote:
>>
>>>
>>>
>> As an aside, I note that the SpecRef lookup (in ReSpec biblio.js) uses
>>> https GET.  I would change that to POST so that if there is a huge query we
>>> don't overflow URL length limits.  I will create an issue about it.
>>>
>>
>> The effective limit is around 2000 chars[1] which should give us over a
>> hundred references. Let's think about fixing it when we cross it, no?
>>
>
> If you insist.  Is the service not able to handle POST requests?
>

Not sure (think I probably purposefully limited it to GET when building the
service, but that's easy to change).

I only mentioned it because if we are integrating definition cross
> reference lookups, we could easily overflow the limit.
>

That would probably be two different end-points, no?

--tobie
Received on Thursday, 2 October 2014 12:24:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:42:21 UTC