The OData protocol
The natural consequence of the release of SAP NetWeaver Gateway was a need to choose a communication protocol that could be handled by the new system. Since the main idea behind the Gateway was to enable non-SAP solutions to easily communicate with the SAP system, without knowledge of Advanced Business Application Programming Objects (ABAP) coding or the database structure, the protocol had to be light, fast, and accessible. Coincidentally, parallel to the development of the Gateway, the first version of Microsoft's Astoria project was also introduced, which fit these needs. SAP joined the efforts with Microsoft and several other companies in an attempt to improve this standard, and eventually, this led to what is now known ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access