> 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).
The main disadvantage is that The Most Popular Database (tm) won't support them effectively. ;-) > 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. Yes, some functionality could be implemented in middleware and some in stored procedures, depending on the module. I can call a stored procedure from a REST API. -- --Josh Josh Berkus PostgreSQL San Francisco _______________________________________________ software mailing list [EMAIL PROTECTED] http://lists.flossfoundations.org/mailman/listinfo/foundations-software
