Jan Algermissen wrote:
> Hi,
>
> On Feb 28, 2006, at 6:29 PM, Gregg Wonderly wrote:
>
> >> This is just impossible if the change occurs at the interface level -
> >> you'd need to upgrade and re-deploy your clients first.
> >
> > In the world of mobile code using Java and Jini, this is not the case.
>
> I keep forgetting that there are actually three opininons to the
> debate, WS-* SOA, Jini SOA and REST. In fact I find Jini rather
> attractive, but had no time to study it closely yet. What I find a
> bit problematic is that it requires Java. But that is orthogonal to
> the architectural style it uses.
Jini requires Java at places where you want direct access to Jini features.
The
Jini Extensible Remote Invocation (JERI) stack provides the ability to plug
other protocols into the invocation layer so that you can bridge the Jini
features on the back side into APIs of other platforms. Jini is Java centric.
The key features of the platform exploit the Java mobile code model. But, it
is
not a brick wall that you can't get other applications and platforms to talk
to.
I've posted several extensive discussions of this on the list in the recent
past.
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/
