On 4/17/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> . I don't think I'll ever
> convince you that there's anything different about WS-* vs. Jini and I'm
> pretty sure you won't convince me Jini does it all.

One problem here is that there are a couple of "political" issues
(e.g. Java vs CORBA vs DCOM) conflated with architectural issues,
which I think comes down to portable code vs portable data.  Another
problem is that "WS-*" is not a pure example of portable data; the red
herring that it is "RPC with angle brackets" is still around, and not
completely unfair given what people actually do with web services in
the real world.  Likewise there is the Worse is Better dynamic that
favors technologies that are already deployed or very easy to deploy
over those that would make the world a better place if only everyone
would just believe in their potential and take some trouble to deploy
them.

My once-upon-a-time infatuation with XML Spaces came from a belief
that they really did hit the sweet spot: The cool features of J/T
Spaces such as associative lookup and leases, but with no need to
drink any flavor of vendor koolaid and with only a necessity to deploy
stock XML technology on the client side.   That doesn't solve many of
the single signon security / multihop reliable messaging / agree on
the semantics of the shared data problems that WS-* wrestles with, of
course.

So, Jini / TSpaces might have failed for all sorts of reasons.  Some
may indeed be political. Some may be related to the basic idea (e.g.
the lease mechanism is "cool" but hard to work with in practice), some
may be due to the fact that nobody with competent marketing department
got behind the ideas, or maybe it's "failed" like hypertext did in the
1980's ... but will be the next decade's Big Thing :-)




 
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