Symmetric web service architecture

In the symmetric web service architecture, both partners host a server and both are able to initiate the communication.

Using the symmetric web service architecture rather than the asymmetrice approach result in:

• The reduction of the number of messages needed to perform the same action; and

• More control for both partners.

The main requirement is that both partners need to host a server.

The following symmetric web service calls are supported in the standard:

Lifecycle of a release using symmetric web service calls

The diagram below demonstrates the lifecycle of a release using asymmetric web service calls.

It is described as follows:

• The DSP requests a lost of releases that are ready for it to obtain. This is done by the DSP calling the record company’s web services;

• The record company then compiles the requested release – the resources are placed onto an SFTP server – and calls the DSP’s web service with the information with the NewReleaseMessage;

• The DSP, now in receipt of the NewReleaseMessage, can download all resources and infest the release; and

• Once all is received, the DSP can inform the record company of the status of the delivery.

Redeliveries are handled in the same way.