sorted by: recent | see :
popular
Content Tagged with services + SOAP
Dare Obasanjo aka Carnage4Life - Explaining REST to Damien Katz
The Web has a particular architecture and it makes sense that if you are deploying a service or API on the Web then it should take advantage of this architecture instead of fighting against it. There are millions of deployed clients, servers and intermediaries that support REST and it makes sense to be compatible with their expectations.
This doesn't mean you have to use DELETE and PUT when POST might suffice. It does mean understanding the difference between using POST versus using PUT to other participants in the Web architecture. Specifically, that PUT is idempotent while POST is not so a client of your service can assume that performing the same PUT two or three times in a row has the same effect as doing it once but cannot assume that for POST.
Dare Obasanjo aka Carnage4Life - Explaining REST to Damien Katz
The uniform interface constraints describe how a service built for the Web can be a good participant in the Web architecture. These constraints are described briefly as follows
1.
Web Services Architecture
Web Services Architecture and formal definition.
Web Services, SOAP e Aplicações Web
Esse artigo traz uma abordagem sobre os Web Standards e arquiteturas que fundamentam as tecnologias relacionadas com Web Services. Um foco especial é dado para o padrão SOAP e os cenários da<sep/>
Web Services Description Language (WSDL) Version 2.0 Part 0: Primer
W3C specification of WSDL 2.0 Part 0 - Primer
Page 1 | Next >>