SL4B Examples: Frameset

This page demonstrates how the master/slave frame functionality provided by SL4B can be used within a website that uses a frameset.

This frame is the "master", which is responsible for establishing and maintaining the connection to the Liberator. The master frame should be one that will always remain loaded within the frameset; failure to do so will result in extra time and bandwidth being wasted each time the master frame is reloaded as the connection to the Liberator needs to reestablished. This may mean that the master frame will not actually display real-time data (if, for example, a navigation bar is selected) or may even be an "invisible" frame (hidden and/or 0 height). Please click here for more information on how this master frame has been configured.

The two frames below this one are slave frames, they use an SL4B subscriber subclass, SL4B_SlaveFrameRttpProvider which proxies all method invocations onto the master frame's RTTP provider. These slave frames do not create independant connections to the Liberator.

SL4B provides a convenient configuration attribute, commondomain which hides away the complexities involved with setting the document.domain property. The commondomain attribute must be set to the same value in both the "master" and "slave" windows.