Got a YouTube account?

New: enable viewer-created translations and captions on your YouTube channel!

English subtitles

← SOAP - Web Development

Get Embed Code
2 Languages

Showing Revision 3 created 05/24/2016 by Udacity Robot.

  1. Okay. Another protocol I'd like to talk about is SOAP. Actually,
  2. I'm just kidding. We are not going to talk about SOAP. SOAP
  3. is based on XML. It's another protocol for communicating between two
  4. machines. If you ever have to deal with it, you'll know why
  5. that I don't even want to bother teaching it. It's very,
  6. very complicated. But what I would like to list for you are
  7. a bunch of other common protocols and formats for communicating across
  8. the Internet. Now SOAP is one of them. We won't be spending
  9. any time on any of these. But lots of people use them.
  10. For example, hip monk, a lot of our data sources communicate via
  11. SOAP. It was invented by Microsoft to make communication online as complicated
  12. as possible. We've got protocol buffers,
  13. which are from Google. Similar to concept
  14. to json, it's a way of encoding different types of data for
  15. sending it over the wire. And there's another one called thrift. This
  16. is by Facebook. Now you've got all sorts of like, plain text,
  17. plus some formats. Now, these are not all. You know? SOAP kind of
  18. defines a whole protocol. Protocol buffers are really, you know, how to encode
  19. data. Thrift is how to encode data over the wire. These, these compare
  20. more to JSON. Soap compares more to HTTP plus JSON. Kind of the
  21. whole package. The protocol and the data type. Of course, you can always
  22. just build your own plain, plain-text, you know, protocol and, and data format,
  23. but I wouldn't recommend doing this. It's not that hard to just use
  24. JSON instead. And then, you know, somebody else who comes along and needs
  25. to use the service, whether it's, you know, outside of your company or
  26. internally, they don't have to figure out, you
  27. know, how to, you know, write all this custom
  28. code to parse, parse your custom stuff. Because JSON
  29. and Thrift and protocol buffers and SOAP, you can
  30. find implementations of these in almost any language. We
  31. mention XML and JSON. Those are also in this
  32. list. Use something that already exists, it'll save everybody
  33. a lot of time. I probably wouldn't use SOAP.