On 5/25/06, Gregg Wonderly <[EMAIL PROTECTED]> wrote:
Okay Mark, so my question is, why would a developer even care what
transport/transfer protocol was used? In the end, isn't it only the data that
goes and the data that returns which matters to the developer? Do they care
about how the two devices interact with each other? At deployment time, someone
will probably care to make the right things talk to the right places. But, as a
developer, do I really care?
Well, I'm no Mark (by any standard :), but let me chip in one piece of knowlegde that I've gained up through my years in software development; developers *really* care about these things, wheter they are important or not; They care about every least significant bit!
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.
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? :)
Alex
--
"Ultimately, all things are known because you want to believe you know."
- Frank Herbert
__ http://shelter.nu/ __________________________________________________
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.
