Can the State File of a Lookout Client Process Write Over the Current Values of a Server Process on Startup ?Primary Software: LookoutPrimary Software Version: 4.5.1 Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: My server process is running remotely. I want to open a client process to see how the server process is doing, but I don’t want the state of the client to change the values of the process file on startup. How can I avoid this? Solution: Every Lookout process has a .l4t file that contains state information. The file stores information about each write-only data member in the process that has a connection (a non-remote connection). Read-only and read/write data members don't have a value stored in the state file. When a process starts up, it reads the state file and sets the corresponding variables to the specified value. This can cause problems on a client process, because undesirable changes could occur to values in the server process. To avoid this problem, use remote connections to the server process. Remote connections are not saved in the state file, but are configured in the Properties of an object. For more information about remote connections, refer to the Lookout Developer's Manual (linked below). Related Links: Lookout Developer's Manual Attachments:
Report Date: 07/21/2003 Last Updated: 11/11/2003 Document ID: 2ZKE1DFL |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
