[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] inter-module communication

From: Hilmar Berger
Subject: Re: [Gnumed-devel] inter-module communication
Date: Tue, 3 Sep 2002 17:44:24 +0200 (CEST)

On Tue, 3 Sep 2002, Karsten Hilbert wrote:

> > B's callback : get copy of X
> Ay, there's the rub ! To my understanding we are signalling
> _change_ of state, not state itself. So a) when I receive a
> change of state event I better update myself and b) when I am
> instantiated I _know_ that I need to update myself to the
> current state of things.
> In any case we are signalling that the _backend_ has changed,
> not the state of some arbitrary frontend object. Extending
> this to server-level listen/notify we are able to even signal
> other clients but that's another matter.

If I get it right all module - module data transfer works through the
backend and only signaling is handled by gmDispatcher ? This would imply
that modules can access only backend objects and for every possible
inter-module data transfer there has to exist at least one corresponding
backend object. That is, after receiving the signal 'patient changed' I
have to access the backend via 'personalia' service.
Sounds good to me, I just got the impression that we would like to supply
the changed data via the parameters of the callback function itself (which
would be possible with gmDispatcher). We will see if the suggested
communication via the backend is to slow and build an lightweight
transfer channel via gmDispatcher only if we really have to.  


reply via email to

[Prev in Thread] Current Thread [Next in Thread]