As a result, it will not be necessary to request additional information for the service consumer in addition, we can still do part of the treatment process internally, asynchronously, without prolonging the client response time or timeout.įinally, this strategy also provides server resource savings since there is no need to request additional information regarding the transaction in progress. This is very desirable because it conforms to one of the great features of the HTTP protocol (which was designed to be Stateless) and allows the transaction to be completely processed in one request. All of this is in a single request handled by the service, which is very important for the processing economy and helps avoid maintaining and/or managing transactions handled by the service, in other words, it conforms to the Stateless behavior. Since all the necessary information is in the same payload, the process of reading and/or parsing the message is simplified. There is an advantage to using this strategy, which is the ability to transmit this tag in the same payload that may contain other information, such as the data needed to process business rules, or better still contain the meta information of the file. Figure 1Īfter the conversion, the String is deposited inside an XML tag, which is part of the Body content of the payload that is being transmitted to the remote server. When we do not use MTOM with SOAP, and the files are transmitted as a MIME attachment of the payload (similar to the process of sending emails containing attachments ), the implementation of the protocol converts the contents of the file that needs to be transmitted, and the result of this conversion is also a binary string in the Base64 format. The project needed to transmit binary files in SOAP Web Services, without using MTOM. Just to contextualize, this strategy was inspired by the architecture of a legacy project that I needed to maintain. SOAP Legacy – Identifying Reusable Concepts This guide will demonstrate one strategy, among many, to implement this integration scenario using resources provided by Mule components. This sounds like a challenge, doesn’t it? Perhaps some additional information for performing business logic processingīut we would like all this information to arrive on the server in the same request.The meta information related to it (e.g., name, content type, size and so on…).Sometimes we need to expose, in our REST API, an upload operation that allows the transmission of:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |