[ckan-dev] Shared access to the database

[Richard Gomes]

Hello,

Suppose I have one CKAN application running, like when we start it in 
the regular way using the paster command.
Now suppose I have "another application" running, which accesses the 
same database, via classes exposed via ckan.model package.

Now suppose that the "another application" adds/updates/deletes objects 
to/from the database.
What would be the impact onto CKAN instance?

To be more precise about the architecture... I'm not willing to dig 
inside the architecture/code/design of CKAN; I'm not willing to create 
plugins for it. I'm happy with what it provides.
I prefer to have my own small applications, which can be web 
applications or not, which are small, simple and under my full control 
and full understanding.
These small applications are responsible for inserting content onto 
CKAN, as well as managing organizations, users and packages.

Then I would like to know what would be the impact of such architecture 
onto a regular CKAN instance.

Any assistance / ideas / sharing of experiences are very much appreciated.

Thanks a lot :)

Richard Gomes
http://rgomes.info
http://www.linkedin.com/in/rgomes
mobile: +44(77)9955-6813
inum <http://www.inum.net/>: +883(5100)0800-9804

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130917/8a1b2719/attachment-0001.html>