> Arguing on this list is one thing. I would not want to argue endlessly
> in my organization, but neither would I want to provide both. I don't
> see that as practical at all if one approach would work.
>
> Clearly those that provide both demostrate that either could work with
> some amount of effort, so then the point is to choose one. But only
> one works with the majority of languages, tools, and existing adopted
> standards and knowledge. It ain't WS-* so there seems to be no
> practical reason to go down that path.
Obviously not everyone agrees with you that all the world's software
integration problems were solved in 1992.
If REST is the silver bullet then I'm afraid many problems are wearing
kevlar preventing the bullet from going through.
Sanjiva.
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.
