>
>> So one response might be "do both". Another response might be
>> "start with HTTP and URI's. Do something additional or instead if
>> the need arises."
>
> Which is how I think you should approach Jini if you are using Java.
> Start with Jini and native object exchanges via the RMI programming
> model. When you need something different, you have tools to do
> something different. This is not typically the case when starting
> with WS-* and SOAP.
Expanding that out a bit, a co-worker and I have been experimenting
with Gigaspaces (which includes Jini, Rio, etc. And Intel Capital has
in investment in GS.)
What we are doing now is starting with HTTP, URIs, and Atom and then
looking at where to use the GS capabilities both on the implementation
side (integration with legacy systems, etc.) as well as on the
"client" side.
A "client" can use the system via HTTP-based resources directly,
eventually we'll look at XMPP as well, or through Jini
capabilities. That could include SOAP as a "legacy" capability,
although many of my co-workers would cringe at my labeling SOAP as
"legacy".
-Patrick
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
