On tis, 2012-07-10 at 08:59 +0200, Björn Harrtell wrote: > Hey all, > > I've begun an implementation of the proposed HTTP API [1] (with some > changes) using node.js > > The project lives at > https://github.com/bjornharrtell/postgresql-http-server and > basic functionality is in place. > > Feedback appriciated! > > [1] http://wiki.postgresql.org/wiki/HTTP_API
The problem I see with this is that if someone else were to take this wiki page and the email thread that preceded it, and tried to implement it, it would look similar but completely different in detail to yours. If there isn't anything like a standard for this out there, it's just going to be another proprietary API/protocol, except that it is transported over HTTP. I'm also not sure about mangling together some of the proposed use cases. I can see the value in exposing the database structures over HTTP for browsing and exploration. But is JSON the right format for this? If you used, for example, XML with some stylesheets, you could easily produce lists and tables in a browser, which would serve this much better. On the other hand, I can see the value of this for embedded or mobile applications. But then you don't need the whole database metadata stuff. A simple and efficient query pass-through would be enough and easier to design. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
