Book Contents | Book Index | Master Index | Previous Chapter | Next Chapter
Search STEP Tools Web Support

26.1 Overview

The RoseServer class is a subclass of the RoseRepository class. This class holds the functions used to move design data between secondary storage and main memory. There is only one RoseServer instance, and it can be found using the RoseInterface::server() function. The server object is used internally by the ROSE library. Applications should not need to use this object.

The RoseServer class manages the memory workspace a provided by the RoseInterface class. The following RoseInterface functions return information kept by the RoseServer object:

    void RoseInterface::clearWorkspace();
    void RoseInterface::saveWorkspace();
     
    RoseBoolean RoseInterface::isInWorkspace(char * design_name);
     
    List(RoseDesign) * RoseInterface::workspaceDesigns();
    List(String) *     RoseInterface::workspaceDesignNames();

The RoseServer methods have counterparts in the ROSE interface object, so you should rarely need to use the server directly. The server does, however, offer more detailed control over the procedures for finding objects in secondary storage and bringing them into main memory.


26.2 findDesign()

RoseDesign * findDesign(
	const char * name,
	const char * as_name = NULL
	);

The findDesign() function is the same as the RoseInterface::findDesign() function, except for the addition of an optional "as_name" parameter. If an "as_name" parameter is given, the design object is read in and named "as_name". If a design with this name already exists in memory, the routine will fail and return null.

 

| Book Contents | Book Index | Master Index | ST-Developer Home | Previous Chapter | Next Chapter |