[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mico-devel
Subject:    Re: Writing a persistent POA
From:       Frank Pilhofer <fp () informatik ! uni-frankfurt ! de>
Date:       2000-09-25 20:20:12
[Download RAW message or body]

On Thu, Sep 21, 2000 at 11:29:45AM +0200, Pascal Bleser wrote:
>
> >  Admittedly, they are a little complex for that purpose. That's because
> > they build upon each other, and persistency is the last feature to be
> > added.
>
> Hmm... what do you mean with "the last feature to be added" ?
>

 demo/poa/account-1 is basic and straightforward. demo/poa/account-2 adds
a ServantManager, and demo/poa/account-3 adds persistence on top of that,
while persistence could very well be demonstrated without a ServantMana-
ger.

>
> So, registering a (POA-based) servant in the IMR is enough to have it
> started on demand ? Or does it *have* to be persistent, too ?
>

 It works only with persistent servants, as the IOR of a transient
servant changes between server re-starts, which does no good for
object reachability.

	Frank


-- 
 + Frank Pilhofer                        fp@informatik.uni-frankfurt.de  +
 |                                      http://www.uni-frankfurt.de/~fp/ |
 +---- Life would be a very great deal less weird without you.  - DA ----+

[prev in list] [next in list] [prev in thread] [next in thread]