Re: CORS performance

Dale Harvey <dale@arandomurl.com> wrote:
> With Couch / PouchDB we are working with an existing REST API wherein every
> request is to a different url (which is unlikely to change), the performance
> impact is significant since most of the time is used up by latency, the CORS
> preflight request essentially double the time it takes to do anything

I understand that currently the cost of this API is 2*N and you want
to reduce the 2 to 1 instead of reducing the N, even though N is
usually much larger than 2.

What is it about PouchDB and CouchDB that causes them to require
preflight for all of these requests in the first place? What is
difficult about changing them to not require preflight for all of
these requests?

Cheers,
Brian

Received on Thursday, 19 February 2015 11:31:25 UTC