> On 6. May 2020, at 17:40, Adam Kocoloski wrote:
>
> When we looked at some of our internal usage data we found that _update had
> measurably higher adoption than the rendering functions, so we didn’t push so
> hard on deprecating it yet.
>
> I’d feel better about removing this endpoint if
When we looked at some of our internal usage data we found that _update had
measurably higher adoption than the rendering functions, so we didn’t push so
hard on deprecating it yet.
I’d feel better about removing this endpoint if there was a clear plan to
provide alternative server-side partial
+1
> On May 6, 2020, at 08:04, Jonathan Hall wrote:
>
> +1
>
>> On 5/6/20 1:57 PM, Jan Lehnardt wrote:
>> Hey all,
>>
>> it appears we missed an item in our 3.0 deprecations list and we should
>> clear this up.
>>
>> We have as of yet failed to capture consensus here about the
>> deprecatio
+1
On 5/6/20 1:57 PM, Jan Lehnardt wrote:
Hey all,
it appears we missed an item in our 3.0 deprecations list and we should
clear this up.
We have as of yet failed to capture consensus here about the
deprecation of the _update endpoint. I think we *have* consensus here,
but we didn’t make it st
+1.
> On 6 May 2020, at 12:57, Jan Lehnardt wrote:
>
> Hey all,
>
> it appears we missed an item in our 3.0 deprecations list and we should
> clear this up.
>
> We have as of yet failed to capture consensus here about the
> deprecation of the _update endpoint. I think we *have* consensus here,
Hey all,
it appears we missed an item in our 3.0 deprecations list and we should
clear this up.
We have as of yet failed to capture consensus here about the
deprecation of the _update endpoint. I think we *have* consensus here,
but we didn’t make it stick in writing.
To recap: the _update endpoi
> On 6. May 2020, at 12:55, Sebastien wrote:
>
> Awesome news, thanks to everyone involved!
>
> A quick question about the JWT authentication support (greatest news in
> this release for my project). Are there plans for Couch to support
> extracting JWT tokens from a cookie?
> In some scenari
FYI: I’ve removed this email address from the list.
Best
Jan
—
> On 6. May 2020, at 09:53, IdeaStack Support wrote:
>
> dev@couchdb.apache.org,
>
> Thank you for contacting our support team. A support ticket has now been
> opened for your request. You will be notified when a response is made
Dear community,
Apache CouchDB® 3.0.1 and 3.1.0 have been released and are available for
download.
Apache CouchDB® lets you access your data where you need it. The Couch
Replication Protocol is implemented in a variety of projects and products that
span every imaginable computing environment
dev@couchdb.apache.org,
Thank you for contacting our support team. A support ticket has now been opened
for your request. You will be notified when a response is made by email. The
details of your ticket are shown below.
Subject: [couchdb-www] branch asf-site updated: feat: 3.1.0
Priority: Medi
10 matches
Mail list logo
