Sorry,
I cannot say anything about our project for instance, but when it will be
released I will be allowed to speak about this.
G�rard Borreill
Bruno Dumant wrote:
> Gerard BORREILL wrote:
>
> > Thank you very much for your answer,
> >
> > Maybe I will implement a distributed garbage collector.
> >
> > Who knows the exact consequences of having no distributed garbage
> > collector ?
>
> I think that it is exactly what you have experienced : memory leaks.
> Note that RMI/IIOP does not provide a garbage collector, which means
> that remote garbage collection must be implemented by the applications.
>
> > I would like to know if it implies that only the skeletons on the
> > server side are never collected, while the server is running.
> > I have a method in a Remote class that returns a Remote object. If a
> > client gets a remote reference on this object, and the client stops,
> > is my remote object never collected because it is related to its
> > skeleton ?
>
> I am afraid yes. The server is no more collectable as soon as it is
> exported (using the exportObject method, or a UnicastRemoteObject
> constructor). It becomes recollectable if it is unexported. Clients are
> not affected by this.
>
> Regards,
>
> Bruno
>
> PS : could you tell us what kind of project you're working on ?
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonathan".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
