|
| |
IERUApplicationThis interface is implemented by the Application object, which is the top level eRoom object. Through the IERUApplication interface, it allows a user context to be established or verified, provides access to eRoom site-level interfaces, current eRoom server as well as facilities. The Application object replaces the eRoom Server Manager (ERUSvrManager) object. If you are developing in a Microsoft .NET language, use the NetApplication object instead of Application object. (Both objects implement the IERUApplication interface.) Note for ASP DevelopersIn some cases, when using SAAPI in ASP, you might need to ensure that eRoom's storage subsystem remains loaded. Do this by storing an IERUApplication (eRoom.Application or eRoom.NETApplication) either in the user's session, or in an ASP application object in global.asa. Note that this is the only eRoom object/interface that should ever be stored on the session or in application-scope objects. This is to ensure that database connections are not held open. The following example shows how you might store the eRoom application object in the user's session. When the user's session times out, the reference will be dropped. Note that eRoom server will keep storage loaded within the IIS process. This should only be a concern if your SAAPI application is running outside the context of IIS. 'EXAMPLE ASP Session Helper function: ' Get eRoom Application Object from user session; Creates and adds to session if it's not already there. Function GetSessionApplication() if isObject(Session("eRoomApplication")) then set GetSessionApplication = Session("eRoomApplication") else dim app set app = CreateObject("eRoom.Application") set Session("eRoomApplication") = app set GetSessionApplication = app end if End Function |
Home |