Mechanisms to support object-oriented version control operations

• US 8,055,619 B2
• Filed: 06/05/2008
• Issued: 11/08/2011
• Est. Priority Date: 06/05/2008
• Status: Expired due to Fees

• Current Assignee: RPX Corporation
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Lundberg, Karin Stella, Street, William, Thurgood, Brent, Vasudevan, Rajesh, Scheuber-Heinz, Volker Gunnar, Lowry, Lee Edward, Grossbart, Zack
• Primary Examiner(s): Wong, Leslie
• Application Number:
  US12/133,492
• Publication Number:
  US 20090307278A1
• Time in Patent Office: 1,251 Days
• Field of Search: 707/638, 707/695, 707/806, 707/999.203, 707/999.107
• US Class Current: 707/638
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor

Abstract

Mechanisms to support object-oriented version control operations are provided. A user manipulates and views a project from an object viewpoint and within an object module. The user performs version control operations using object handles. The object handles are resolved to specific file references and the specific file references are used to process legacy version control commands utilizing a legacy version control system in a manner that is transparent to the user.

Claims

1. A machine-implemented implemented in a non-transitory computer-readable medium and for execution on a machine, the method, comprising:

receiving, at the machine, from a framework driver service an object handle for an object;

parsing, by the machine, an object definition for the object to resolve multiple file names and file paths associated with the object, a definition for the object spans multiple physical files identified by the multiple file names and the file paths; and

returning, by the machine, to the framework driver service the multiple file names and the file paths for the framework driver service and performing legacy version control operations on behalf of a user that initiated a version control operation using just the object handle and not the multiple file names and the file paths, the user provides the object handle and the version control operation and transparent to the user the multiple file names and the file paths are used with the legacy version control operations for processing the version control operation against the multiple physical files for the definition of the object.

2. The method of claim 1 further comprising,

subsequently receiving, at the machine and from the framework driver service a set of different file names;

parsing, by the machine, files associated with the different file names to resolve different object handles for different objects defined in the files; and

returning, by the machine, to the framework driver service the different object handles for delivery to a user that is attempting to find object associations to particular known files via the different file names via interaction with the framework driver service.

3. The method of claim 1, wherein parsing further includes dynamically and in real time parsing the object definition.

4. The method of claim 1, wherein parsing further includes acquiring preconfigured parsing rules specific to an object type that is associated with the object, wherein the parsing rules provide dynamic instructions for parsing the object definition.

5. The method of claim 4, wherein parsing further includes identifying an embedded object in the object definition for a different object type and consulting an adapter service for that different object type, and asking the adapter service to parse that embedded object.

6. The method of claim 1, wherein parsing further includes locating the object definition in response to the object handle.

7. The method of claim 1, wherein returning further includes returning to the framework driver service content data associated with the multiple file names.