> On 5/25/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
>> But, as a developer, do I really care?
>
...
> It's not only data that goes from one end to the other, and possibly back
> again; there is a significant amount of human knowledge and semantics that
> gets parsed, packed and floated through the whole development cycle; human
> emotions are attached to modules (rage against the caching module, sweet
> lovin' the export module, etc); opinions on "best way to do something" is
> *exactly* what developers care about! Code is only half of what developers
> do.
Yes, this list is probably at least the other half for some... :-)
> You may say that on some level that we should all be grown-ups and just
> agree on one way to do things, that WS-* just makes sense and that any other
> silly RESTful notion is a toy compared to the control inherited by SOAP and
> so forth. But hey, if *you* didn't care, why are we even arguing on this
> mailing-list? :)
Okay, I'll agree that emotions are everywhere. But, if we have to argue about
who's emotions are better, I think I'm gonna half to sit that one out...
Technically, my argument is away from SOAP. My argument is that wire transport
shouldn't be part of the puzzle that a developer thinkgs about. The dumbing
down of the interface for messaging/RPC causes people to think of problems with
less flexibility. What that implies, to me, is that they will me worse
decisions about how to manage data integrity and coherency, because they have
few language based tools at their disposal.
Gregg Wonderly
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.
