Ditto.  Or should I say +1 ;-)
 
FWIW that point has been made clear previously on this forum.
 
Eric

----- Original Message ----
From: Sanjiva Weerawarana <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, April 17, 2006 2:02:08 PM
Subject: technology and politics (was: Re: [service-orientated-architecture] Re: TSpaces)

Dan, I'm going to bow out of this debate. 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.

IMO its not realistic to think that a technology "makes it", or not,
purely based on its technical merits. Maybe Jini can indeed do it all,
but that's irrelevant: does MSFT support it? What about IBM? What about
Oracle? What about SAP? What about IONA? What about Macromedia? What
about a host of other companies? (No, I won't say "What about
WSO2?" ;-))

You have to accept that Web services does indeed have that going for
itself .. despite all the political and other problems that that
necessarily comes with.

Sanjiva.

On Mon, 2006-04-17 at 18:00 +0100, Dan Creswell wrote:
> Sanjiva Weerawarana wrote:
> > On Mon, 2006-04-17 at 14:27 +0000, patrickdlogan wrote:
> >>> Jini suffers... in order to play you needed their software on every
> >>> box... getting it on every box is not easy.
> >> This is an apples and oranges comparison. Yes, putting a SOAP port is
> >> can be done using an IDE in just four steps. But Jini is more like an
> >> "enterprise service bus". Simple SOAP can be integrated with either
> >> and EBS or Jini.
> >
> > Sorry, you missed the point completely.
> >
> > My point is that to do Jini you need to install some (free, maybe)
> > software from the same vendor on every piece of the puzzle.
> >
>
> Which piece of software are you referring to?  The JVM?  If that's the
> case, no I don't need to install everywhere.  Stuff that can't run a JVM
> can still participate in a Jini environment.
>
> > With Web services, the focus is the opposite: you install software from
> > whoever that claims compliance to support the wire standards.
> >
>
> Surely you want some clear and concise assurance of compliance rather
> than just a claim?
>
> > Do you seriously disagree that there's no fundamental difference in
> > focus on what aspect (wire vs. endpoint) is being defined for the
> > integration standard in WS-* vs. say Jini?
> >
> > I didn't say anything about the size of the software you need to
> > install: I'm sure some vendors WS-* stacks require a boatload of
> > software! That's not at all the point.
> >
>
> Ah, but the size aspect and a bunch of other aspects do matter.  If you
> consider something in complete isolation from a single perspective, you
> maybe get one particular winner.  Mix in a whole load of other issues,
> maybe things aren't so clear cut or maybe you get some other winner
> entirely.
>
> Consider two boxers - one 70Kg and one 120Kg.  If we measure just on
> punching power, the 120Kg boxer likely wins.  But is that all there is
> to boxing?  Of course not, there's speed, reaction time, fitness,
> tactics, technique, range etc.
>
> Dan.
>
>
>
>

> Yahoo! Groups Links
>
>
>

>
>






SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to