Compositing URL spaces using your load balancer

If your Diffusion™ servers are located at a different URL to the Diffusion browser clients hosted by your web servers, you can use a load balancer to composite the URL spaces.

Security features in some browsers prevent web-based Diffusion clients from making requests to your Diffusion server if your Diffusion server is in a different URL space to the web server you use to host your client.

At the top of the image blue lines representing client requests come in. These client requests pass into a grey rectangle labelled 'load balancer'. A note nearby says 'Configure the load balancer to use sticky IP addresses'. From the load balancer, part of the client request is routed on to a set of three grey server icons on the left labelled 'Domain web servers (web.example.com)'. From the load balancer, part of the client request is routed to one of two blue server icons on the right labelled 'Diffusion secondary servers'. A note nearby says 'Diffusion servers handle client connections.' These Diffusion secondary servers are connected to another blue server icon below labelled 'Diffusion primary server (diffusion.example.com)'.

Your web content is hosted on web.example.com and your Diffusion servers are hosted on diffusion.example.com.
The load balancer composites the URL space so that requests to Diffusion at web.example.com are routed to Diffusion servers hosted on diffusion.example.com
To the client, both the web and the Diffusion content appear to be hosted on web.example.com. This avoids any cross-domain security issues.

If you choose not to use your load balancer to composite the URL spaces, you can set up cross-domain policy files that allow requests to the different URL spaces.