RMI conundrum

Thread view:

VisionSet - 23 Dec 2005 17:25 GMT

I send an object over RMI

myRemoteMethod(myObject);

But I want to do something to myObject after it has been safely serialised
(ie I don't want the server to know of the change I want to make). I don't
want to have to wait until the remote method returns. If I fire the method
off in its own thread then I can ascertain when that thread is running, but
I can't be sure when myObject has been serialised.
I realise I can get round this by cloning myObject but is there an
alternative. Seems a pain to have to implement cloning throughout my object
tree just for this, especially when serialisation is going to do it for me -
just that I can't get at it - or can I?

--
Mike W

Reply to this Message

Mandar Amdekar - 02 Jan 2006 22:29 GMT

No automatic way as near as I can tell.

However, you could override the serialization / externalization method
in the class that is the root of your complex data structure, and as
part of it, implement the observer pattern. Then you simply hook up
one or more observers to all root objects on creation (for simplicity)
and in the observer, use some sort of a delay before triggering the
change logic.

Reply to this Message

VisionSet - 02 Jan 2006 22:42 GMT

> No automatic way as near as I can tell.
>
[quoted text clipped - 4 lines]
> and in the observer, use some sort of a delay before triggering the
> change logic.

Good idea, I may well do that.
I'll have to check that the order of serialisation runs children first, root
last though.

--
Mike W

Reply to this Message

RMI conundrum

Free Magazines