Sim IJskes - QCG wrote:
Peter Firmstone wrote:
Note that when you export your service it's proxy is stored in
Marshalled form until the client discovers it, while in Marshalled
form only, it cannot participate in DGC. In that case you might want
to hold a reference for a period of time (Lease), long enough to allow
your clients to discover the service.
Isn't that what i originally described? The serialized export of the
server is stored in the network buffers and the DGC does not start until
deserialized in the client?
What are you suggesting here, that for every factory that produces an
exported reference we should implement a Jini Lease (on the server side)?
I have a class named LeasedSmartProxy which I use for all of my exported,
per/user service endpoints (authenticated access to the server creates a unique
proxy for each user). There is a Lease that is renewed by the smart proxy by
using a LeaseRenewalManager on unmarshalling.
I've never been fond of how DGC has some hiccups that I've not been able to
understand, so I've always just rolled my own DGC.
Gregg Wonderly
