Method and apparatus for providing drawing collaboration on a network

• US 7,149,959 B1
• Filed: 10/16/2000
• Issued: 12/12/2006
• Est. Priority Date: 03/25/1999
• Status: Active Grant

• Current Assignee: Autodesk, Inc.
• Original Assignee: Autodesk, Inc.
• Inventors: Jones, Stuart Edward, Sweat, Mark Edward
• Primary Examiner(s): Hong, Stephen
• Assistant Examiner(s): LUDWIG, MATTHEW J
• Application Number:
  US09/690,326
• Time in Patent Office: 2,248 Days
• Field of Search: 715/500.1, 715/751, 715/753, 719/328, 719/329, 345/751, 345/752, 709/205, 709/225, 709/217, 707/10, 707/201
• US Class Current: 715/234
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A method, apparatus, and article of manufacture for an application programming interface (API) on a client computer that enables access to architectural project information stored across the internet on a server site. The server site maintains an organization for the architectural information in the form of containers for storing, managing, and sharing files for one or more architectural projects, wherein the files comprise drawings, documents, communications, and tasks related to the architectural projects. The API of the invention permits third parties to create custom clients or permit direct access to a site hosted on a server. Such an API operates with both thick (.exe) and thin (.html) clients. The API establishes/obtains a connection between the client and the server to enable such access. For example, if the user desires to store a file on the server site, the user selects the appropriate server site/folder from within an application program executing the API. The API may then require the user to logon and confirms that the user has appropriate access permissions to work with the server site/folder. Once confirmed, the connection session is established. During the session, the user may access and download files as desired while maintaining the storage structure of architectural information stored on the server site.

Claims

1. An apparatus for accessing architectural project information on the internet, comprising an application programming interface (API), executed by a client computer, having a plurality of procedures that provide for an organization of containers for storing, managing and sharing files for one or more architectural projects, and that allow an application program executed by the client computer to access architectural project information stored across the internet on a server site, wherein:

the server site has defined user access permissions;

the application program invokes the procedures of the API;

the invoked procedures obtain a connection across the internet between the application program with appropriate user access permissions on the client and the server site;

the architectural project information accessed by the application program using the API are organized in containers for storing, managing, and sharing files for one or more architectural projects, wherein the files comprise drawings, documents, communications, and tasks related to the architectural projects; and

the architectural project information is created using an interactive web site hosted on the server, and one or more areas of the interactive web site provide for;

modification and organization of;

a display of the interactive web site;

site members of the interactive web site;

one or more projects including storing, organizing, and displaying drawings and text files in project folders and standard folders; and

project members of the one or more projects including defining access permissions for project members to access the project folders, the standard folders, the drawings, and the text files;

wherein project related administration tasks are available if a user is working with the project folders and such project related administration tasks are not available when working with the standard folders.

2. The apparatus of claim 1 wherein the procedures invoke wizard methods for retrieving a file from the server to the client.

3. The apparatus of claim 1 wherein the procedures invoke wizard methods for uploading a file from the client to the server.

4. The apparatus of claim 1 wherein the procedures provide access to information relating to a specific file on the server.

5. The apparatus of claim 1 wherein the procedures provide access to information relating to a specific folder on the server.

6. The apparatus of claim 1 wherein the procedures provide for uploading a file from the client to the server.

7. The apparatus of claim 6 wherein the procedures unlock the file for editing after the upload is complete.

8. The apparatus of claim 1 wherein the procedures provide for retrieving a file from the server to the client.

9. The apparatus of claim 8 wherein the procedures lock the file for editing after the retrieval is complete.

10. The apparatus of claim 1 wherein to obtain the connection between the client and the server, the procedures require a user to log on to verify the appropriate user access permissions.

11. The apparatus of claim 1 wherein:

a session object is maintained once the connection is established; and

a lifetime of the session object controls connection caching such that the user does nor need to log on with each operation requested.

12. The apparatus of claim 1 wherein information relating to execution of the procedures is maintained in an activity log.

13. A method for accessing architectural project information on the internet, comprising invoking one or more procedures of an application programming interface (API) executed by a client computer, wherein:

the plurality of procedures provide for an organization of containers for storing, managing and sharing files for one or more architectural projects, and allow an application program executed by the client computer to access architectural project information stored across the internet on a server site;

the server site has defined user access permissions;

the procedures of the API obtain a connection across the internet between the application program with appropriate user access permissions on the client and the server site;

the architectural project information accessed by the application program using the API are organized in containers for storing, managing, and sharing files for one or more architectural projects, wherein the files comprise drawings, documents, communications, and tasks related to the architectural projects; and

the architectural project information is created using an interactive web site hosted on the server, and one or more areas of the interactive web site provide for;

modification and organization of;

a display of the interactive web site;

site members of the interactive web site;

one or more projects including storing, organizing, and displaying drawings and text files in project folders and standard folders; and

project members of the one or more projects including defining access permissions for project members to access the project folders, the standard folders, the drawings, and the text files;

wherein project related administration tasks are available if a user is working with the project folders and such project related administration tasks are not available when working with the standard folders.

14. The method of claim 13 wherein the procedures invoke wizard methods for retrieving a file from the server to the client.

15. The method of claim 13 wherein the procedures invoke wizard methods for uploading a file from the client to the server.

16. The method of claim 13 wherein the procedures provide access to information relating to a specific file on the server.

17. The method of claim 13 wherein the procedures provide access to information relating to a specific folder on the server.

18. The method of claim 13 wherein the procedures provide for uploading a file from the client to the server.

19. The method of claim 18 wherein the procedures unlock the file for editing after the upload is complete.

20. The method of claim 13 wherein the procedures provide for retrieving a file from the server to the client.

21. The method of claim 20 wherein the procedures lock the file for editing after the retrieval is complete.

22. The method of claim 13 wherein to obtain the connection between the client and the server, the procedures require a user to log on to verify the appropriate user access permissions.

23. The method of claim 13 wherein:

the procedures maintain a session object once the connection is obtained; and

a lifetime of the session object controls connection caching such that the user does not need to log on with each operation requested.

24. The method of claim 13 wherein information relating to execution of the procedures is maintained in an activity log.

25. An article of manufacture embodying an application programming interface (API) that is executed by a client computer, wherein the API includes a plurality of procedures that provide for an organization of containers for storing, managing and sharing files for one or more architectural projects, and that allow an application program executed by the client computer to access architectural project information stored across the internet on a server site, wherein:

the server site has defined user access permissions;

the application program invokes the procedures of the API, the invoked procedures obtain a connection across the internet between the application program with appropriate user access permissions on the client and the server site;

the architectural project information accessed by the application program using the API are organized in containers for storing, managing, and sharing files for one or more architectural projects, wherein the files comprise drawings, documents, communications, and tasks related to the architectural projects; and

the architectural project information is created using an interactive web site hosted on the server, and one or more areas of the interactive web site provide for;

modification and organization of;

a display of the interactive web site;

site members of the interactive web site;

one or more projects including storing, organizing, and displaying drawings and text files in project folders and standard folders; and

project members of the one or more projects including defining access permissions for project members to access the project folders, the standard folders, the drawings, and the text files;

wherein project related administration tasks are available if a user is working with the project folders and such project related administration tasks are not available when working with the standard folders.

26. The article of manufacture of claim 25 wherein the procedures invoke ward methods for retrieving a file from the server to the client.

27. The article of manufacture of claim 25 wherein the procedures invoke wizard methods for uploading a file from the client to the server.

28. The article of manufacture of claim 25 wherein the procedures provide access to information relating to a specific file on the server.

29. The article of manufacture of claim 25 wherein the procedures provide access to information relating to a specific folder on the server.

30. The article of manufacture of claim 25 wherein the procedures provide for uploading a file from the client to the server.

31. The article of manufacture of claim 30 wherein the procedures unlock the file for editing after the upload is complete.

32. The article of manufacture of claim 25 wherein the procedures provide for retrieving a file from the server to the client.

33. The article of manufacture of claim 32 wherein the procedures lock the file for editing after the retrieval is complete.

34. The article of manufacture of claim 25 wherein to obtain the connection between the client and the server, the procedures requite a user to log on to verify the appropriate user access permissions.

35. The article of manufacture of claim 25 wherein:

a session object is maintained once the connection is established; and

a lifetime of the session object controls connection caching such that the user does not need to log on with each operation requested.

36. The article of manufacture of claim 25 wherein information relating to execution of the procedures is maintained in an activity log.