Difference between revisions of "SOAP"
Wiki-JoWalsh (talk | contribs) m |
Wiki-JoWalsh (talk | contribs) m |
||
| Line 1: | Line 1: | ||
| + | People say "SOAP vs [[REST]] so there is a [[REST]] page. | ||
| + | |||
| + | ---- | ||
| + | |||
The Draft Implementing Rules for Network Services for geographic data under the INSPIRE directive may mandate a SOAP interface for access to all OGC web services. This means WMS, WFS, WCS, CSW et al - even when the behaviours of a SOAP interface are not fully-described in the OGC specifications. | The Draft Implementing Rules for Network Services for geographic data under the INSPIRE directive may mandate a SOAP interface for access to all OGC web services. This means WMS, WFS, WCS, CSW et al - even when the behaviours of a SOAP interface are not fully-described in the OGC specifications. | ||
Revision as of 06:06, 13 July 2007
People say "SOAP vs REST so there is a REST page.
The Draft Implementing Rules for Network Services for geographic data under the INSPIRE directive may mandate a SOAP interface for access to all OGC web services. This means WMS, WFS, WCS, CSW et al - even when the behaviours of a SOAP interface are not fully-described in the OGC specifications.
Are there user community experiences, documentable, to do with SOAP working or not working in the wild? It is easy to collect a lot of opinions and a lot of references to opinions. It is necessary to put together a set of clear basic use cases and do as much benchmarking and testing as possible. If people are offering and documenting both SOAP and the common REST style interfaces to their repositories, what do the access statistics look like? etc.
Help?
References
- http://www.somebits.com/weblog/tech/bad/whySoapSucks.html From Nelson Minar, who worked on several SOAP services for Google.