How does Content Upload/Download work over Web Services?
During the course of Oracle Content DB development, we looked at some of the major Web Services client development platforms and their support for various Web Services standards, including support for attachments. A number of clients either did not support attachments, or had key functionality missing such as the ability to support MIME attachments. Because our Web Services are based on HTTP and require client-side cookie support, we are able to provide content upload and download through the Oracle Content DB WebDAV Server. The WebDAV server must be presented with the same user session cookie that is established through the RemoteLoginManager or ServiceToServiceLoginManager login operation. The client, once identified by the WebDAV server, only needs to perform a standard HTTP GET or PUT to download or upload content. HTTP PUT calls can also participate in Web Service-initiated transactions; this means that a rollback on the transaction will also reverse any content changes. Core Item
