Abstract: A data processing apparatus configured as a browser (70) is described for use with a distributed database management utility (72) which handles the accessing of data defining virtual environments via the Internet/World Wide Web (74). Both browser (70) and management utility (72) maintain copies of data files obtained via the Web and passed to the browser, with a memory management stage (80) detecting when apparatus memory reaches a predetermined level of fullness. Based on a stored and system-updated table (84) identifying the passing of data files from management utility to browser, the memory manager (80) identifies which of the management utility held copies of the files to delete in order to create memory space.

Abstract: A data processing apparatus configured as a browser (70) is described for use with a distributed database management utility (72) which handles the accessing of data defining virtual environments via the Internet/World Wide Web (74). Both browser (70) and management utility (72) maintain copies of data files obtained via the Web and passed to the browser, with a memory management stage (80) detecting when apparatus memory reaches a predetermined level of fullness. Based on a stored and system-updated table (84) identifying the passing of data files from management utility to browser, the memory manager (80) identifies which of the management utility held copies of the files to delete in order to create memory space.

Abstract: A data browser is described for accessing data defining virtual environments via the Internet/World Wide Web. In conjunction with at least one store (44) of virtual environment assets, such as audio, video, graphics textures and so forth, a list (62) is maintained recording the identity of the stored assets received via the Web, suitably in the form of their respective URL's. Browser applications requiring assets from the store (44) scan the master list to determine whether a particular asset is already stored there on encountering a program requirement for that asset to avoid the need to access the remote source of asset data via the Web. Where the assets are distributed over more than one storage device (44, 60), each device is suitably provided with such a contents list.