Help !!! why does the client need to specify codebase

Question

Anyone,
I'm trying out a dynamic class loading tutorial.
my question is why does the client need to define
java.rmi.server.codebase.
I can understand why the server needs it, as it is downloading classes
it does not have information about. But why does the client need to specify the codebase

Answer 1

Lets say you have a Remote interface with a method:
void compute(Task task);
Now, the clients of this remote interface want supply
a zillion of custom tasks to be executed on the
server, but how the hell the server knows where to get
the actual classes for those tasks?You fool. its for the server to hand the client the reference to a stub, or to specify FOR the client where the stubs are, so that the CLIENT can get a reference to them, to make the call.
This is where the
client codebase comes to the scene. Client codebase......you mean codebase info that is sent TO the client, so it can find the classes.
A client annotates
it and it gets written to the manifest part of any
serializable object (Task implentation) being passed
over then net so the server could find and download
the actual class of the object.
Rubbish.
I hope I made myself clear. as mud.
You might want to check
out this link also:
http://java.sun.com/products/jdk/1.2/docs/guide/rmi/cod
base.htmlI read this and i still dont see anything about CLIENT codebase. I see stuff about codebase, and the server trying to make the client aware of where it can get the relevant classes.
What a fool you are. Dont bother replying. I have had enough of your autocratic rubbish.
>