Look at the scenario below:
Assume that some client has aleady registerd a callback object by calling setSomeClass() on theFoo.
What happens when theFoo.bar() is called on the server? it's instance of SomeClass is 'living' in another JVM so when it in turn calls someClass.someMethod(...) will it cause changes to the client?
This may seem like a stupid questio, but I want to be sure before I proceed with this.
Most of the tutorials I've seen seem to give the impression that RMI is only good for `querying` the server and haven't found anything solid showing how the server can get the client to do something (the efffect I'm trying to achieve by registering a callback).
TIA.
Assume that some client has aleady registerd a callback object by calling setSomeClass() on theFoo.
What happens when theFoo.bar() is called on the server? it's instance of SomeClass is 'living' in another JVM so when it in turn calls someClass.someMethod(...) will it cause changes to the client?
This may seem like a stupid questio, but I want to be sure before I proceed with this.
Most of the tutorials I've seen seem to give the impression that RMI is only good for `querying` the server and haven't found anything solid showing how the server can get the client to do something (the efffect I'm trying to achieve by registering a callback).
TIA.