From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Álvaro Hernández Tortosa <aht(at)8kdata(dot)com> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <obartunov(at)gmail(dot)com> |
Subject: | Re: about google summer of code 2016 |
Date: | 2016-02-22 22:34:47 |
Message-ID: | 21714.1456180487@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
=?UTF-8?Q?=c3=81lvaro_Hern=c3=a1ndez_Tortosa?= <aht(at)8kdata(dot)com> writes:
> On 22/02/16 05:10, Tom Lane wrote:
>> Another variable is that your answers might depend on what format you
>> assume the client is trying to convert from/to. (It's presumably not
>> text JSON, but then what is it?)
> As I mentioned before, there are many well-known JSON serialization
> formats, like:
> - http://ubjson.org/
> - http://cbor.io/
> - http://msgpack.org/
> - BSON (ok, let's skip that one hehehe)
> - http://wiki.fasterxml.com/SmileFormatSpec
Ah, the great thing about standards is there are so many to choose from :-(
So I guess part of the GSoC project would have to be figuring out which
one of these would make the most sense for us to adopt.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Álvaro Hernández Tortosa | 2016-02-22 22:42:33 | Re: about google summer of code 2016 |
Previous Message | Álvaro Hernández Tortosa | 2016-02-22 22:23:30 | Re: about google summer of code 2016 |