> I'm a bit late to the game here but it strikes me that this isn't
> an either/or decision. There are appropriate times to use WS-*
> and appropriate times to use REST
I suppose that if one had a requirement that the system be tightly
coupled, that SOA/WS would beat out REST there.
And I'm not saying that to be snarky; just pointing out the fact that
SOA/WS fails to separate the concerns of interface and implementation
(as previously discussed on this list), while REST does so very
effectively.
Mark.
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.
