What is the Best Coding Practice for Web Services with Large Attachments?
(Doc ID 1062552.1)
Last updated on FEBRUARY 13, 2024
Applies to:Web Services - Version 10.1.2.0.2 to 10.1.3.4.0
Information in this document applies to any platform.
Building SOAP JAX-RPC style web services, which will transmit a large file attachment can cause considerable performance overhead, depending on the size of the attachment. Considering that SOAP itself was designed more for interoperability rather than efficiency, a large attachment can cause performance bottlenecks. Added to this (from the client side perspective) there is considerable overhead spent in XML encoding of the SOAP message payload which is basically serializing and marshalling of the payload before it is transmitted to the server.
An example application might be one in which a web service connects to a back end content server (or repository) to load a large file for transmission to a web application on another server.With this in mind, what is the best and most performent methodology for transmitting a large attachment to the client ( for example 1 megabyte to 100 megabytes and higher) ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document