> 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.
On some computers you would install some Jini components. On others
you may have just SOAP components. On others you may have yet other
components.
> With Web services, the focus is the opposite: you install software from
> whoever that claims compliance to support the wire standards.
Please explain how, using only these individual SOAP toolkit vendors,
you intend to implement the functionality offed by Jini.
> 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?
Jini components can communicate with non-Jini over networking
protocols. Rather than "wire" vs. "API" instead I am arguing the
salient difference between SOAP and Jini is (1) functionality, and (2)
a Jini-based system can include those SOAP components.
> 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.
Good. Then we agree on at least one point! 8^)
-Patrick
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/
