[
https://issues.apache.org/jira/browse/COUCHDB-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978024#action_12978024
]
Benoit Chesneau commented on COUCHDB-1012:
--
i'm +1 for that.
> Utility to help
[
https://issues.apache.org/jira/browse/COUCHDB-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Teofilov updated COUCHDB-1011:
--
Attachment: COUCHDB-1011.patch
Initial implementation. The document IDs separators ar
I might throw in a line about the secure version being SSL based and
the majority of clients in existence will expect there to be a second
port. Not to mention I have no idea if its even possible to detect
encryption after the socket's been accepted without ruining the
communication protocols.
On
I can see that's true in new protocols, but they can't be claiming
that http -> https upgrade works as needed, because that requires a
change to a huge number of clients.
Agree with Noah, it's probably just a rote response. Something about
'secure port' just niggles them, I guess.
B.
On Wed, Jan
Don't read much into their response. It's probably a canned one for people who
ask for secure ports. They're basically just asking for more justification, I
think. That's why I want some feedback. Want to make sure I'm making a strong
case for it.
On 5 Jan 2011, at 21:09, Paul Davis wrote:
> M
That sounds pretty good to me.
On Wed, Jan 5, 2011 at 9:00 PM, Noah Slater wrote:
> I'd like to get some peer review on my response to IANA here.
>
> CouchDB is a special use-case of HTTP 1.1 as justified in my previous
> application for TCP 5984. It is, however, still bound by the common
> lim
Most odd. Your response looks good to me, but judging from the email
you're responding to, they've already specifically said that reasoning
is no longer considered. Perhaps you should ask which modern security
protocols they're talking about and some pointers on where we might
look for an "automagi
I'd like to get some peer review on my response to IANA here.
CouchDB is a special use-case of HTTP 1.1 as justified in my previous
application for TCP 5984. It is, however, still bound by the common limitations
of HTTP 1.1 over SSL/TLS. In theory, HTTP 1.1 provides a mechanism to upgrade
an es
[
https://issues.apache.org/jira/browse/COUCHDB-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana closed COUCHDB-1008.
--
Resolution: Fixed
Applied to trunk
> Add socket_options to the ini .configuration
>
On Wed, Jan 5, 2011 at 6:31 PM, Robert Newson wrote:
> have previous releases shipped with these mochiweb bugs?
Not mochiweb, ibrowse :)
Maybe, but I think some parts of ibrowse were rewritten for release 2.0.0.
>
> I'm a bit equivocal on whether we should hold 1.0.2 up for these now.
>
> On Wed
have previous releases shipped with these mochiweb bugs?
I'm a bit equivocal on whether we should hold 1.0.2 up for these now.
On Wed, Jan 5, 2011 at 6:14 PM, Filipe David Manana wrote:
> On Wed, Jan 5, 2011 at 11:37 AM, Filipe David Manana
> wrote:
>> I'm now -1 on it until Ibrowse issue
>> ht
On Wed, Jan 5, 2011 at 11:37 AM, Filipe David Manana
wrote:
> I'm now -1 on it until Ibrowse issue
> https://github.com/cmullaparthi/ibrowse/issues#issue/24 is fixed. It
> affects push replications only.
> However a new Ibrowse release is going to be made very soon (today or
> tomorrow), perhaps w
branch 1.1.x with worse database read/write performance
---
Key: COUCHDB-1013
URL: https://issues.apache.org/jira/browse/COUCHDB-1013
Project: CouchDB
Issue Type: Bug
Reporter:
[
https://issues.apache.org/jira/browse/COUCHDB-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana updated COUCHDB-682:
--
Affects Version/s: 0.10
0.10.2
0.11.1
Thanks Nikolai.
On Wed, Jan 5, 2011 at 4:26 PM, Nikolai Teofilov wrote:
> Filipe, I will try to see what I can do.
>
> On 05.01.2011, at 11:13, Filipe Manana (JIRA) wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/COUCHDB-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comm
Filipe, I will try to see what I can do.
On 05.01.2011, at 11:13, Filipe Manana (JIRA) wrote:
>
>[
> https://issues.apache.org/jira/browse/COUCHDB-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977711#action_12977711
> ]
>
> Filipe Manana co
[
https://issues.apache.org/jira/browse/COUCHDB-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977792#action_12977792
]
Randall Leeds commented on COUCHDB-1012:
Apparently, "pkg-config works on multipl
I'm now -1 on it until Ibrowse issue
https://github.com/cmullaparthi/ibrowse/issues#issue/24 is fixed. It
affects push replications only.
However a new Ibrowse release is going to be made very soon (today or
tomorrow), perhaps with that exact patch. So should be pretty quick.
On Tue, Jan 4, 2011 a
[
https://issues.apache.org/jira/browse/COUCHDB-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977711#action_12977711
]
Filipe Manana commented on COUCHDB-1011:
Nikolai, I think to start out, a text bo
[
https://issues.apache.org/jira/browse/COUCHDB-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977698#action_12977698
]
Benoit Chesneau commented on COUCHDB-1012:
--
neither is erlang :) We could make i
20 matches
Mail list logo
