http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10662
David Cook <dc...@prosentient.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|Needs Signoff |In Discussion
--- Comment #29 from David Cook <dc...@prosentient.com.au> ---
I've been thinking a bit about the connexion_import_daemon.pl, and how it uses
/cgi-bin/koha/svc/import_bib. This uses the "Staged Marc Management" backend
without exposing it to users.
Unfortunately, I think that service is hard-coded just to work with
connexion_import_daemon.pl... so I might need to alter
/cgi-bin/koha/svc/import_bib a bit... but that might be an option. I actually
quite like that idea overall as it provides a more loosely coupled system.
I'm also tempted to change the existing system so that you define OAI-PMH
servers, and then create OAI-PMH tasks for those servers. This information
would all be stored in the database. Then, when you wanted to run a task, you
could click "Run" on the Web UI, and it would send the task to the daemon.
I haven't 100% thought out how the Web UI and the daemon will communicate yet.
While that above paragraph sounds good, what happens if the daemon dies for
some reason? If it requires a message from the Web UI, it'll need a human to
restart it.
Another thought is to let it access the MySQL database... in that case the Web
UI would change a field in the database (like "state" to indicate that it
should be running), and then tell the daemon something like "READ 15" to read
the task from the database with an ID of 15. That way... if the daemon crashes,
a server-side process could detect the crash and then tell the daemon to
re-start itself... and when the daemon is re-starting, it could just look in
the database for any tasks that it should be running, and get back on track.
If it has database access, it's not really that loosely coupled which would be
unfortunate...
Actually, another idea... the Web UI could send the task, and the daemon could
write it away to a temporary file which it cleans up after it's finished a
task. If it crashes and gets restarted, it can check its temporary files to see
what it was in the middle of doing. Yeah... that's probably a better idea.
Another idea would be to use shared memory... but I would need to do some more
research into that one.
--
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
