|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
|
Message #183454
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
 |
What?
The problem is that when we say "Web services", the "web" part of it implies HTTP and REST and all that other stuff. It's time we faced reality: SOAP is not just for doing stuff over the Internet. It's time we started calling them what they are: XML services. Ted has totally lost me with the distinction that he's trying to make here. SOAP doesn't require HTTP... but you could also say that XML services don't require SOAP. Going further, services don't require XML.
We might as well just call them what they are: services.
--John
|
|
|
Message #183598
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
What? hopefully clarified
The problem is that when we say "Web services", the "web" part of it implies HTTP and REST and all that other stuff. It's time we faced reality: SOAP is not just for doing stuff over the Internet. It's time we started calling them what they are: XML services. Ted has totally lost me with the distinction that he's trying to make here. SOAP doesn't require HTTP... but you could also say that XML services don't require SOAP. Going further, services don't require XML.We might as well just call them what they are: services.--John
XML services without SOAP miss an important part of what SOAP provides, which is to say, framing and extensibility points. SOAP "just" provides a place to hang additional out-of-band information, such as confidentiality/integrity/authentication headers (a la WS-Security), guaranteed delivery semantics (a la WS-Reliability or WS-ReliableMessaging), and so on, without having to "pollute" your actual message content. The same sort of stuff is present in most wire protocols, in fact, for the same sorts of reasons. (Take a look at JMS or MSMQ, you'll see the same basic construct there, too.)
So while it's fair to say that "services don't require XML" (a quick look at Jini pretty much confirms that idea, IMHO), I think it is necessary to say that "XML services require SOAP". To exclude SOAP is to miss a large opportunity for standardization.
|
|
|
Message #183603
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
What? hopefully clarified
>> "XML services require SOAP". To exclude SOAP
>> is to miss a large opportunity for standardization
If it's about SOAP after all, then why not call it "SOAP Services"? R.
|
|
|
Message #184388
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Ted Neward: "Long live XML services!"
XML services fits the bill for Web Services, SOAP, XML-RPC...
Point is: XML sucks.
When the REAL engineers starts getting back to the IT industry, they will hopefully set things straight.
|
|
|
| Featured SectionFeatured SectionFeatured Section |
|
|
|
|
| Weekly Blogs UpdateWeekly Blogs UpdateWeekly Blogs Update |
|
|
|
|
| Featured BlogsFeatured BlogsFeatured Blogs |
|
|
Dmitri Maximovich has written a blog on optimizing CMP EJB performance in WebLogic, by addressing optimistic concurrency, along with some of the implications of doing so.
|
Brian McCallister looks at the Lucene search engine and shows us how to index and retrieve objects from a sample Student application.
|
Cedric Beust has been in a position to actually code with JDK 5 for over six months. He has written up his thoughts on the new features, and how he has found them to be in practice.
|
Mike Clark has started a series of entries of letters that you wish you could write to your boss. It consists of concepts which seem so obvious to us, but which the bosses don't get.
|
Brian McCallister has been playing with JDO 2 fetch groups, ZODB, thinking about TranQL, playing with Prevayler, and looking at TORPEDO.
|
Frank talks about fear and how it can derail efforts to find and solve scalability and performance problems. He has seen a lot of fear on his various engagements, and here he talks about why, and how.
|
Brian McCallister has kindly rambled on about IoC, and design in web applications. He discusses what has worked well for him (and others) in the last year.
|
Matt Raible went to the Denver JUG meeting with Neal Gafter, and Joshua Bloch. They discussed the new features of Java 5, and Matt details the features, and when to use them.
|
|
Featured Blogs Archive
|
|
|
