Search the archives!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
HashTable
- From: ted@xxxxxxxxxx (Ted Neward)
- Subject: HashTable
- Date: Wed, 29 Nov 2000 11:05:38 -0800
So long as the stub on the client remains "alive" (that is, able to
communicate back to the server and renew its Lease), the object on the
server will also remain alive, guaranteed--the DGC portion of the RMI Specs
guarantee that. I can't see any reason why holding a Remote reference in a
HashTable would be a problem, except for the usual "what if the server
crashes" issue, and that's an issue regardless of whether the reference is
held in a HashTable or as a regular reference.
Ted Neward
{C# || Java} Instructor, DevelopMentor (http://www.develop.com)
http://www.javageeks.com/~tneward
----- Original Message -----
From: "Scott Smith" <ssmith2_list@xxxxxxxxxxx>
To: <ted@xxxxxxxxxx>; <advanced-java@xxxxxxxxxxxxxxxx>
Sent: Wednesday, November 29, 2000 5:40 AM
Subject: Re: HashTable
> What do you think would happen if we kept a reference to a Remote object
> (which I guess would really be a reference to a stub?) and the remote
object
> was gc'd on the remote server and then we tried to use the reference we
> kept? I wonder if you would get a NullPointerException?
>
> I've never actually dealt with this notion so I may be totally on the
wrong
> path.....
>
>
> >From: "Ted Neward" <ted@xxxxxxxxxx>
> >To: "Milind Kulkarni" <milind.kulkarni@xxxxxxxxxxxxxxx>,
> ><advanced-java@xxxxxxxxxxxxxxxx>
> >Subject: Re: HashTable
> >Date: Wed, 29 Nov 2000 02:19:01 -0800
> >
> >What was their reasoning for saying that storage of remote objects was a
> >problem?
> >
> >Ted Neward
> >{C# || Java} Instructor, DevelopMentor (http://www.develop.com)
> >http://www.javageeks.com/~tneward
> >
> >----- Original Message -----
> >From: "Milind Kulkarni" <milind.kulkarni@xxxxxxxxxxxxxxx>
> >To: <advanced-java@xxxxxxxxxxxxxxxx>
> >Sent: Tuesday, November 28, 2000 10:24 PM
> >Subject: HashTable
> >
> >
> > >
> > >
> > > Dear All,
> > >
> > > Core Java ( Cornell & Horstmann, Prentice-Hall 1997) mentions that
there
> >are
> > > problems in putting a remote objects into a hashtable. I belive that
> >this
> > > problem is no longer exist in the latest version of JDK(1.2.2 & 1.3).
We
> >plan to
> > > use hashtable to store global data while implemeting our own session
> >manager.
> > > Can anybody confirm this???
> > >
> > > Regards,
> > > Milind
> > >
> > >
> > >
> > >
> > > ---
> > > To unsubscribe, mail advanced-java-unsubscribe@xxxxxxxxxxxxxxxx
> > > To get help, mail advanced-java-help@xxxxxxxxxxxxxxxx
> >
> >
> >---
> >To unsubscribe, mail advanced-java-unsubscribe@xxxxxxxxxxxxxxxx
> >To get help, mail advanced-java-help@xxxxxxxxxxxxxxxx
>
>
____________________________________________________________________________
_________
> Get more from the Web. FREE MSN Explorer download :
http://explorer.msn.com
---
To unsubscribe, mail advanced-java-unsubscribe@xxxxxxxxxxxxxxxx
To get help, mail advanced-java-help@xxxxxxxxxxxxxxxx
- References:
- HashTable
- From: Scott Smith
- HashTable
- Prev by Date: NEW TWIST: Finding ALL instances of a Class
- Next by Date: unexplained memory usage phenomenon
- Previous by thread: HashTable
- Next by thread: HashTable
- Index(es):