>
>
> Such is the problem there are times where I dont want the user to be able
> to alter a returned object's state.
>
Thats easy just add a lock variable that take the ( Caller) as a prameter to
set.
Or its not public.
Check that on each method invoction which effects state.
I'm not sure of the utility of having and object wich no methods can be called
on.
This is nothing more than a more generic form of thread synchronization.
In fact a quick and dirty way to do it is to grab the thread lock for the
object in a method that never returns.
i.e block on and I/O that never finishes. Or simpler force a deadlock.
This will deadlock the calling thread forever though so it is very rude : )
Mike
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
