Re: Why, at least, serialization?

On Jun 21, 2009, at 10:22 AM, Niclas Hedhman wrote:
> Jini's mission is built around the concept of location-independence,  
> configuration-free and self-healing networked systems.
>
> So, to answer 'serialization'; No it is up to the service and proxy  
> to agree to any private protocol they like. It can be RMI, or it  
> could be a home-brewed protocol over UDP, SPX or what not. The  
> service contract is only between the client and the proxy running in  
> the client.
>
Yes, but I think that the question is about the requirements for one  
service's proxy to be passed to another (the primary example being a  
lookup service), for which there needs to be some agreement for how  
the second service can transfer the first's proxy-- and the  
expectation there is that the proxy supports RMI marshalling semantics  
(and thus serialization) even if second service doesn't actually use  
RMI to do such a transfer.

-- Peter

--------------------------------------------------------------------------
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]