Gervas Douglas wrote:
> I was thinking in terms of the basic middleware providing
> cross-enterprise connectivity, but as you observe it does not really
> affect your answer.  Now if one were to use a language-agnostic
> implementation of tuple spaces....

Gervas, as I commented in Anne's reply, I'm not seeing the "missing" 
language-agonisticisms.  The tools in the Jini Technology Starter Kit are 
written in Java.  The specification requires Java to implement, and many of the 
features make explicit use of Java's mobile code.  That starts to look an quite 
a bit like a language dependent toolset.

However, TCP/IP is a binary protocol, as is HTTP, and many others that we find 
implemented across a wide range of languages and platforms.

The features of Jini are the tools that you have access to.  If you use Java, 
you have access to mobile code and native language transport of RPC invocations.

If you don't use Java, you have access to the Javaspaces API, distributed 
leasing, distributed transactions and any Jini services that you create with 
explicit support of the Configuration mechanism that will allow you to plug in 
exporters, invocation layer factories and endpoints.

It's all in how you view the use of the system's components in your SOA.  Just 
like many different implementation of many different technologies.  
Interactions 
across programming languages limit your choices in some ways.  With Jini, like 
Web Services implementations, you have a choice of how to interface.

The use of mobile code is what differentiates Jini from the what will come out 
of all the WS standards that are developing to finally add the pieces needed to 
effectively and correctly handle partial failure in a distributed systems 
environment.

You may not ever use Jini, but someday you'll have access to tools that have 
recreated it for you...

Gregg Wonderly





 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/service-orientated-architecture/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to