I think we shouldn't end documents with newlines, because a canonical
representation of json won't included a trailing newline, which can
cause complications with end to end integrity checks.
-Damien
Along those lines, I hereby present four options and an informal vote:
* Accept the patch (or a modified version) and add newline chars
+0
* Reject the patch (and any modified version) and do not add
newlines chars
+0
* Further discussion, to be decided before we release 0.9
+1
* Further discussion, to be decided after we release 0.9
On Jan 26, 2009, at 7:21 AM, Noah Slater wrote:
On Mon, Jan 26, 2009 at 01:07:26PM +0100, Christopher Lenz wrote:
On 23.01.2009, at 23:42, Noah Slater wrote:
We need to decide a resolution for COUCHDB-107:
End JSON responses with newline char
This ticket has a patch, and it's been discussed to death on the
mailing list.
FYI, I uploaded a version of the patch updated to work with trunk.
Thanks for this!
I would like to see votes from the other PMC members please. :)
--
Noah Slater, http://tumbolia.org/nslater
