Abstract: Systems and methods are disclosed for providing proprietary access to a server. The disclosed systems and methods may include receiving a first service request from a client. The first service request may include a client identifier. Furthermore, the disclosed systems and methods may include creating a session identifier when it is determined that the client identifier is valid and transmitting the session identifier to the client. Moreover, the disclosed systems and methods may include receiving a second service request from the client. The second service request may include the session identifier and client data that may have at least one of a proprietary format and a proprietary scheme. In addition, the disclosed systems and methods may include servicing the second service request when it is determined that the session identifier received in the second service request is valid.

Abstract: A change list tracking mechanism supports features that require a record of values that have been modified in a document of a project management software application. Examples of the features supported include multiple undo, report generation, and audit logging. The change list tracking mechanism includes object containers and change lists. Each object container includes objects that are associated with properties of the document. A user who wants to be notified of specific modifications creates the change list to track modifications made to a specific object property in a particular object container. A property value identified in the change list may be modified by any user that accesses the document. The corresponding object container provides information about the modification to the change list. The user is identified and notified of the modification.

Abstract: Backend data is received from a computer program product such as a hard disk or other long term data storage. The backend data is structured using nodes that are associated with a unique identifier such as a GUID. The nodes are addressable using the unique identifier, and backend data items are associated with corresponding addressable nodes such that the backend nodes can be quickly accessed. Front-end data can be received from a computer program product such as a hard disk or other long term data storage. The front-end data is structured using nodes that are associated with a unique identifier such as a GUID. The nodes are addressable using the unique identifier, and front-end data items are associated with corresponding addressable nodes such that the front-end nodes can be quickly accessed.