[omniORB] Authentication; Garbage Collection

[BaileyK at schneider.com]

If using a default servant, then that servant would keep track of what's in
memory based on object ID.  If a request arrives with an ID that doesn't
have state data currently in memory, it will have to be fetched.

If not using a default servant, then you would use a servant manager to do
the same thing.  I think the ServantLocator with the preinvoke and
postinvoke methods would give you the most control, or a ServantActivator
would allow you to only fetch evicted objects as needed.

Kendall



                                                                                                                         
                      Alex Suzuki <ml at cynox.ch>                                                                          
                      Sent by:                             To:       Duncan Grisby <duncan at grisby.org>                   
                      omniorb-list-bounces at omniorb-        cc:       omniorb-list at omniorb-support.com                    
                      support.com                          Subject:  Re: [omniORB] Authentication; Garbage Collection    
                                                                                                                         
                                                                                                                         
                      07/22/2004 01:24 PM                                                                                
                      Please respond to as                                                                               
                                                                                                                         
                                                                                                                         




Duncan,

Duncan Grisby wrote:
 > No, because you have a database. As long as you persist the object
 > state before you evict the servant, it doesn't matter if a servant is
 > evicted when the associated object reference is still held by a
 > client. If a client tries to use the object, the servant will be
 > reactivated and populated from the data in the database.

How do I accomplish this (reactivating the servant and populating it
with data from the DB)? When do I have to do this, and where?

Say I have my (by now famous) Person interface which has a method
doThis() and it is called on a reference to a servant that has been
evicted. Do I have to do this reinternalization for every method or
is there a transparent way to do it? Again, I'm sorry for asking these
(possibly stupid) questions, a simple keyword or reference to a
paragraph in some spec. will do fine.

cheers,
   Alex
--
Alex Suzuki | as at cynox.ch | http://n.ethz.ch/student/asuzuki/
"Computer Science is no more about computers than astronomy
  is about telescopes." - E.W.Dijkstra
%- warning: aggressive spam filter enabled for this address

_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list