Re: Why, at least, serialization?

>> So, this means that the default LUS server needs to receive at least a=

>> serializable object to maintain the Jini system as it was specified (v=
ery=20
dynamic
>> and agnostic in location matters)...

>There is no "default" LUS. All LUSes in the same group are registering
>all services in parallel to provide for redundancy, scalability and
>robustness to intermittent network problems. Otherwise correct.^

When I refer default LUS I mean the default LUS implementation algorithm=20=

(reggie) not a particular LUS running on the federation. Sorry it was my=20=

mistake.=20
I already studied UpnP, SLP etc but Jini is my target. Why? I dont know?=20=

because the Java world that is fashinating. I have a tiny JVM for that de=
vice=20
(made at my home) with tcp/IP sockets but no serialization (no room for t=
hat=20
:-( ). I am looking for ways to enter in the jini federation with that de=
vice (for=20
consume and for supply jini services, obviously tiny services).

I just have one idea that is operate on LUS default implementation. May b=
e the=20
LUS could start accept ALSO other form of things which are not serializab=
le=20
objects .=20

Please, could you comment this solution?


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]