Re: Why, at least, serialization?

Niclas Hedhman wrote:
> On Mon, Jun 22, 2009 at 4:32 PM, Alex Co<[email protected]> wrote:
>> If my client device do not suports even (de)serialization, is there any way to
>> integrate that device in the jini federation (without using surrogate) in order to
>> give the chance to it to expose and consume Jini services, even sacrificing (a
>> little) the whole jini federation?
> 
> As I mentioned just now, I think you will be in for a tough ride. Even
> surrogate won't help you, since Jini basically requires a full JVM on
> the client, whereas you are much more free to do what you like on the
> server. I think that you may have better luck with either UPnP or
> perhaps SLP. If you are into OSGi, check out r-OSGi which may (I have
> not looked at the details) suit your needs, as I know Jan Rallermeier
> is biased heavily towards the embedded space.

The specification of JERI/RMI and Serialization has a lot of freedom allowed if 
you stick with the term "semantics" and not with the term "specifics".  What has 
to happen is that you need to be able to "act" with behaviors that mean the 
semantic meaning of what should happen but you need to do that by implementing 
the "specifics" of what is known as (de)serialization.

In particular, you can provide end point and invocation layer activities in your 
service endpoint that only require http and transfer XML data.

When you talk about service discovery, than you have a different issue.  Because 
the LUS specification already exists, and because LUS implementations are pretty 
much just Reggie, you have to go to some more direct steps to get a "services 
client endpoint" in your "jini client".

People have done wide and varying things to get a service object active. I've 
heard of http download of a serialized object stream.  You could do this by 
writing a MarshalledObject instance to a file, for example.

But, you could also have all the "classes" "known" in your application and just 
have the client ready to instantiate an instance, and just have "data" 
transported back and forth with XML, or JSON or something else.

There are choices for using services, but not a lot of choices if you want to 
use a ServiceRegistrar instance for your lookup service.

Gregg Wonderly

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