[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] re: callback from event loop in wxPython
From: |
Horst Herb |
Subject: |
Re: [Gnumed-devel] re: callback from event loop in wxPython |
Date: |
Sat, 31 Jan 2004 18:13:53 +1100 |
User-agent: |
KMail/1.5.9 |
On Sat, 31 Jan 2004 16:54, Karsten Hilbert wrote:
> - legacy medical practice app without document archive selects
> a patient
> - it attaches to gnumed
> - it tells gnumed to call up its document archive plugin for
> that patient
> - it tells gnumed to stay locked onto that patient
> - user works with the gnumed gui handling various documents
> - user decides to add a vaccination for this patient - this is
> possible but it is not possible to change to another patient
> from inside the gui
> - user "returns" to legacy app thereby releasing the gnumed
> lock
How about:
legacy app call XML-RPC service "gnumed archiver" with parameter patient ID
- the XML-RPC server gets the call
- spawns an instance of the archiver module
- returns a handle
legacy app is happy, instance can close:
- XML-RPC call to server "close handle <n>"
- server closes instance with handle <n>
If legacy app wants gnumed module to do someting, it just accesses the
module's API via the same XML-RPC server, passing handle, command and
parameters as parameters.
On the client side, you can have a simple XML-RPC client that can be piped
into via stdin/stdout or whatever.
Horst