> >3. use unique "ids" that are associated with each object (23, 46, 67) in
>
> You mean each thread object?
actually, *all* objects. but get_threads will only return those ids
that correspond to the threads (alongwith the rest of thread info)
> >the VM. "threads" lists all the threads but instead of numbering them,
> >simply prints the unique id associated with the thread. all user
>
> Who generates the id? Are the id's persistant across sessions?
the JDI implementation. no.
> Option 3 sounds best, followed by option 1.
ok
amit