[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Proposal for LedgerSMB 1.5: Move to Pg 9.2 and use JSON for extended attributes

On Tue, Sep 18, 2012 at 7:12 AM, Andres Basile <..hidden..> wrote:
Hello Chris,
My personal opinion would be to move to 9.2 and using json as protocol between server and client, but, my understanding is that it will need a new kind of client, able to request, understand json and fill the html, also, it would need a new kind of handler. Instead of work on that, I would focus efforts on database and store procedures, my personal experience contributing to this project was to reach the database layer and to don't know what to do. What I mean is, if the database had a full set of procedures working as abstraction layer it would be easy for development to add new extensions. 

Also something you (and others) may find useful for integration work:

I got tired of staring at Perl a couple weeks ago and threw together a message queue abstraction.    I got tired again today and bundled it up as a PostgreSQL extension for PostgreSQL 9.1 and higher.

You can play with it at http://code.google.com/p/pg-message-queue/

The idea is that it creates message queues that you can hook into using db triggers, stored procedures, etc, and messages become available on db commit.  It has LISTEN/NOTIFY support but you can just as easily poll from a cron job if you only want to run daily.  Right now queues support binary, text, or xml payloads, and I would like to add JSON when I get around to bumping up the required version to 9.2.

Best Wishes,
Chris Travers