Artwork

Content provided by Tomasz Nurkiewicz. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tomasz Nurkiewicz or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

#74: SOAP: (not really) Simple Object Access Protocol

4:14
 
Share
 

Manage episode 328634859 series 2680464
Content provided by Tomasz Nurkiewicz. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tomasz Nurkiewicz or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

SOAP, formerly known as Simple Object Access Protocol, is a messaging standard. SOAP is very broad and general. Technically, it can support request-response, as well as fire-and-forget communication. The underlying protocol is typically HTTP, but there’s nothing against using message brokers. Or even good old SMTP. You know, the one for exchanging e-mails. The communication happens through XML messages. These messages are well-defined and structured. XML schema is agreed upon before any communication.

Read more: https://nurkiewicz.com/74

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

  continue reading

98 episodes

Artwork
iconShare
 
Manage episode 328634859 series 2680464
Content provided by Tomasz Nurkiewicz. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tomasz Nurkiewicz or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

SOAP, formerly known as Simple Object Access Protocol, is a messaging standard. SOAP is very broad and general. Technically, it can support request-response, as well as fire-and-forget communication. The underlying protocol is typically HTTP, but there’s nothing against using message brokers. Or even good old SMTP. You know, the one for exchanging e-mails. The communication happens through XML messages. These messages are well-defined and structured. XML schema is agreed upon before any communication.

Read more: https://nurkiewicz.com/74

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

  continue reading

98 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide