[software] Rapport2

[Dave Rolsky]

On Mon, 27 Oct 2008, Bradley M. Kuhn wrote:

> Also, Dave, Josh Berkus has argued frequently for trying to push some of
> the unchangeable workflow logic (i.e., database integrity certainty)
> down into database stored procedures.  One reason this is helpful is
> that it can often mean someone can write applications directly to the
> database itself, since they are unlikely to "break" anything by not
> using the standard APIs, since the stored procedures will stop them from
> doing something stupid.
>
> Have you considered this for Rapport?

Not really. I do understand the reasoning for doing this, and it has its 
advantages, but it also has a number of disadvantages (no need to go into 
all that here).

Since my first goal is to write something for my animal rights group that 
I can maintain easily, I'm really only interested in doing it "my way" for 
now. My second goal is to build something that I can host and sell as a 
service.

As far as integrating with other apps, I am building the system in a way 
that will make exposing a REST (or REST-like) API fairly easy. The URIs 
are all "cool URIs" and all updates are done with proper REST semantics 
(POST, PUT, DELETE). The code includes various hacks to make this work 
with browsers, but that's largely transparent.

Personally, I think a REST API has greater potential than stored 
procedures, especially for a hosted service, for obvious reasons.


-dave

/*============================================================
http://VegGuide.org               http://blog.urth.org
Your guide to all that's veg      House Absolute(ly Pointless)
============================================================*/