Why, at least, serialization?

(Sorry if this msg is duplicated. Not sure about the registration on this=
 forum)

Hi all,
I am learnnig Jini.

I have a question for you that i till now didnt get an answer:=20
The subject is why serialization for Jini services. Please, read this tho=
ught:

Jini does not mandate the use of rmi as the communication protocol betwee=
n=20
client and server, right?
So, for those that do not want to use rmi, the service interface must at =
least=20
implements serializable, right?

Then, on client side, if client needs to use a jini service it downloads =
service=20
classes definitions by http (for example) and the jini service object com=
es by=20
wire by using serialization on server side and deserialization on client =
side. Then=20
the proxy is constructed on the client side by "joining" the downloaded c=
lasses=20
definitions and the proxy object that arrives to client by deserializatio=
n.

My question is: why it is necessary downloaded class definitions and=20
deserialized proxy object to invoke jini service?

Why not just get the class definitions, instantiate them and call its met=
hods?
What is the role of the proxy object there?


When using mobile code i understand that the proxy object must travel too=
 in=20
order to save data and state by for invoke a Jini method are proxy object=
s=20
really needed too?

Many thanks

Alex

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]