Heterogeneous network file access

• US 7,293,099 B1
• Filed: 09/29/1998
• Issued: 11/06/2007
• Est. Priority Date: 09/29/1998
• Status: Expired due to Fees

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Kalajan, Kevin E.
• Primary Examiner(s): Etienne; Ario
• Assistant Examiner(s): BURGESS, BARBARA N
• Application Number:
  US09/163,246
• Time in Patent Office: 3,325 Days
• Field of Search: 709/227, 709/237, 709/224, 709/217, 709/232, 709/243, 709/246, 709/203, 709/219, 709/229, 709/230
• US Class Current: 709/230
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

A method for a client to access data files residing on a first data server through a network includes coupling a heterogenous proxy server to the first data server through a first local network protocol, selectively receiving at the heterogeneous proxy server a data file from the first data servers by employing the first local network protocol, translating the data file into a format compatible with transmission through the network, and transmitting the translated data file to the client across the network.

Claims

1. A method implemented by a server, comprising:

receiving a request from a first client to browse contents of a first file system on a first data server, wherein the first data server implements the first file system for managing file access and storage, and wherein the first client is unaware that the first data server implements the first file system;

selecting a first protocol interpreter from a plurality of different protocol interpreters, wherein the first protocol interpreter implements a first file access protocol which enables interaction with the first file system;

invoking the first protocol interpreter to interact with the first file system of the first data sever to obtain therefrom a first list of contents, wherein the first list of contents sets forth a hierarchical listing of at least a portion of the contents of the first file system on the first data server, the first list of contents comprising one or more directories and zero or more files; and

sending at least a portion of the first list of contents to the first client.

2. The method of claim 1, wherein the first client executes a web browser and submits the request using the web browser.

3. The method of claim 1, wherein the first client does not implement the first file access protocol such that the first client is incapable of interacting directly with the first file system.

4. The method of claim 1, further comprising:

receiving a request from the first client to browse contents of a second file system on a second data server, wherein the second data server implements the second file system, different from the first file system, for managing file access and storage, and wherein the first client is unaware that the second data server implements the second file system;

selecting a second protocol interpreter from the plurality of different protocol interpreters, wherein the second protocol interpreter implements a second file access protocol which enables interaction with the second file system;

invoking the second protocol interpreter to interact with the second file system of the second data sever to obtain therefrom a second list of contents, wherein the second list of contents sets forth a hierarchical listing of at least a portion of the contents of the second file system on the second data server, the second list of contents comprising one or more directories and zero or more files; and

sending at least a portion of the second list of contents to the first client.

5. The method of claim 4, wherein the first client does not implement the second file access protocol such that the first client is incapable of interacting directly with the second file system.

6. The method of claim 1, further comprising:

receiving a request from a second client to browse contents of a second file system on a second data server, wherein the second data server implements the second file system, different from the first file system, for managing file access and storage, and wherein the second client is unaware that the second data server implements the second file system;

selecting a second protocol interpreter from the plurality of different protocol interpreters, wherein the second protocol interpreter implements a second file access protocol which enables interaction with the second file system;

invoking the second protocol interpreter to interact with the second file system of the second data sever to obtain therefrom a second list of contents, wherein the second list of contents sets forth a hierarchical listing of at least a portion of the contents of the second file system on the second data server, the second list of contents comprising one or more directories and zero or more files; and

sending at least a portion of the second list of contents to the second client.

7. The method of claim 6, wherein the second client does not implement the second file access protocol such that the second client is incapable of interacting directly with the second file system.

8. The method of claim 1, further comprising:

receiving a request from the first client to further explore a particular directory on the first data server;

invoking the first protocol interpreter to interact with the first file system of the first data sever to obtain therefrom a second list of contents, wherein the second list of contents comprises zero or more directories and one or more files stored within the particular directory; and

sending at least a portion of the second list of contents to the first client.

9. The method of claim 1, further comprising:

receiving a request from the first client to access a particular file stored on the first data server;

invoking the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom;

determining a file type for the particular file;

generating a set of encoding information based upon the file type of the particular file, wherein the set of encoding information comprises information for causing the first client to execute a particular type of application to process the particular file; and

sending the particular file and the set of encoding information to the first client.

10. The method of claim 9, wherein sending the particular file and the set of encoding information comprises:

sending the particular file and the set of encoding information as an electronic mail file to the first client.

11. The method of claim 10, wherein the electronic mail file comprises Multipurpose Internet Mail Extension (MIME) information.

12. The method of claim 9, wherein determining a file type for the particular file comprises:

determining a file extension for the particular file; and

processing the file extension to determine a file type for the particular file.

13. The method of claim 12, wherein processing comprises:

determining a Multipurpose Internet Mail Extension (MIME) type for the file extension.

14. The method of claim 13, wherein the set of encoding information comprises the MIME type.

15. The method of claim 1, further comprising:

receiving a request from the first client to compress a particular file stored on the first data server;

invoking the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom;

compressing the particular file to derive a compressed version; and

invoking the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to store the compressed version onto the first data server.

16. The method of claim 1, further comprising:

receiving a request from the first client to send a particular file stored on the first data server to a recipient;

invoking the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom; and

sending the particular file to the recipient without first downloading the particular file to the first client.

17. The method of claim 1, further comprising:

receiving a request from the first client to create a new directory on the first data server; and

invoking the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to create the new directory on the first data server.

18. The method of claim 1, further comprising:

receiving a request from the first client to store a new file onto the first data server;

receiving the new file from the first client; and

invoking the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to store the new file onto the first data server.

19. The method of claim 1, further comprising:

receiving a search request from the first client comprising a set of search criteria;

processing the set of search criteria to derive one or more search commands;

invoking the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to implement the one or more search commands; and

receiving one or more sets of search results from the first file system.

20. The method of claim 19, further comprising:

processing the one or more sets of search results to derive a processed set of search results; and

sending the processed set of search results to the first client.

21. The method of claim 19, wherein the set of search criteria comprises a Boolean operation and/or a wild card.

22. An apparatus, comprising:

a mechanism for receiving a request from a first client to browse contents of a first file system on a first data server, wherein the first data server implements the first file system for managing file access and storage, and wherein the first client is unaware that the first data server implements the first file system;

a mechanism for selecting a first protocol interpreter from a plurality of different protocol interpreters, wherein the first protocol interpreter implements a first file access protocol which enables interaction with the first file system;

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data sever to obtain therefrom a first list of contents, wherein the first list of contents sets forth a hierarchical listing of at least a portion of the contents of the first file system on the first data server, the first list of contents comprising one or more directories and zero or more files; and

a mechanism for sending at least a portion of the first list of contents to the first client.

23. The apparatus of claim 22, wherein the first client executes a web browser and submits the request using the web browser.

24. The apparatus of claim 22, wherein the first client does not implement the first file access protocol such that the first client is incapable of interacting directly with the first file system.

25. The apparatus of claim 22, further comprising:

a mechanism for receiving a request from the first client to browse contents of a second file system on a second data server, wherein the second data server implements the second file system, different from the first file system, for managing file access and storage, and wherein the first client is unaware that the second data server implements the second file system;

a mechanism for selecting a second protocol interpreter from the plurality of different protocol interpreters, wherein the second protocol interpreter implements a second file access protocol which enables interaction with the second file system;

a mechanism for invoking the second protocol interpreter to interact with the second file system of the second data sever to obtain therefrom a second list of contents, wherein the second list of contents sets forth a hierarchical listing of at least a portion of the contents of the second file system on the second data server, the second list of contents comprising one or more directories and zero or more files; and

a mechanism for sending at least a portion of the second list of contents to the first client.

26. The apparatus of claim 25, wherein the first client does not implement the second file access protocol such that the first client is incapable of interacting directly with the second file system.

27. The apparatus of claim 22, further comprising:

a mechanism for receiving a request from a second client to browse contents of a second file system on a second data server, wherein the second data server implements the second file system, different from the first file system, for managing file access and storage, and wherein the second client is unaware that the second data server implements the second file system;

a mechanism for selecting a second protocol interpreter from the plurality of different protocol interpreters, wherein the second protocol interpreter implements a second file access protocol which enables interaction with the second file system;

a mechanism for invoking the second protocol interpreter to interact with the second file system of the second data sever to obtain therefrom a second list of contents, wherein the second list of contents sets forth a hierarchical listing of at least a portion of the contents of the second file system on the second data server, the second list of contents comprising one or more directories and zero or more files; and

a mechanism for sending at least a portion of the second list of contents to the second client.

28. The apparatus of claim 27, wherein the second client does not implement the second file access protocol such that the second client is incapable of interacting directly with the second file system.

29. The apparatus of claim 22, further comprising:

a mechanism for receiving a request from the first client to further explore a particular directory on the first data server;

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data sever to obtain therefrom a second list of contents, wherein the second list of contents comprises zero or more directories and one or more files stored within the particular directory; and

a mechanism for sending at least a portion of the second list of contents to the first client.

30. The apparatus of claim 22, further comprising:

a mechanism for receiving a request from the first client to access a particular file stored on the first data server;

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom;

a mechanism for determining a file type for the particular file;

a mechanism for generating a set of encoding information based upon the file type of the particular file, wherein the set of encoding information comprises information for causing the first client to execute a particular type of application to process the particular file; and

a mechanism for sending the particular file and the set of encoding information to the first client.

31. The apparatus of claim 30, wherein the mechanism for sending the particular file and the set of encoding information comprises:

a mechanism for sending the particular file and the set of encoding information as an electronic mail file to the first client.

32. The apparatus of claim 31, wherein the electronic mail file comprises Multipurpose Internet Mail Extension (MIME) information.

33. The apparatus of claim 30, wherein the mechanism for determining a file type for the particular file comprises:

a mechanism for determining a file extension for the particular file; and

a mechanism for processing the file extension to determine a file type for the particular file.

34. The apparatus of claim 33, wherein the mechanism for processing comprises:

a mechanism for determining a Multipurpose Internet Mail Extension (MIME) type for the file extension.

35. The apparatus of claim 34, wherein the set of encoding information comprises the MIME type.

36. The apparatus of claim 22, further comprising:

a mechanism for receiving a request from the first client to compress a particular file stored on the first data server;

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom;

a mechanism for compressing the particular file to derive a compressed version; and

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to store the compressed version onto the first data server.

37. The apparatus of claim 22, further comprising:

a mechanism for receiving a request from the first client to send a particular file stored on the first data server to a recipient;

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom; and

a mechanism for sending the particular file to the recipient without first downloading the particular file to the first client.

38. The apparatus of claim 22, further comprising:

a mechanism for receiving a request from the first client to create a new directory on the first data server; and

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to create the new directory on the first data server.

39. The apparatus of claim 22, further comprising:

a mechanism for receiving a request from the first client to store a new file onto the first data server;

a mechanism for receiving the new file from the first client; and

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to store the new file onto the first data server.

40. The apparatus of claim 22, further comprising:

a mechanism for receiving a search request from the first client comprising a set of search criteria;

a mechanism for processing the set of search criteria to derive one or more search commands;

a mechanism for invoking the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to implement the one or more search commands; and

a mechanism for receiving one or more sets of search results from the first file system.

41. The apparatus of claim 40, further comprising:

a mechanism for processing the one or more sets of search results to derive a processed set of search results; and

a mechanism for sending the processed set of search results to the first client.

42. The apparatus of claim 40, wherein the set of search criteria comprises a Boolean operation and/or a wild card.

43. A computer readable medium, comprising:

instructions for causing one or more processors to receive a request from a first client to browse contents of a first file system on a first data server, wherein the first data server implements the first file system for managing file access and storage, and wherein the first client is unaware that the first data server implements the first file system;

instructions for causing one or more processors to select a first protocol interpreter from a plurality of different protocol interpreters, wherein the first protocol interpreter implements a first file access protocol which enables interaction with the first file system;

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data sever to obtain therefrom a first list of contents, wherein the first list of contents sets forth a hierarchical listing of at least a portion of the contents of the first file system on the first data server, the first list of contents comprising one or more directories and zero or more files; and

instructions for causing one or more processors to send at least a portion of the first list of contents to the first client.

44. The computer readable medium of claim 43, wherein the first client executes a web browser and submits the request using the web browser.

45. The computer readable medium of claim 43, wherein the first client does not implement the first file access protocol such that the first client is incapable of interacting directly with the first file system.

46. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a request from the first client to browse contents of a second file system on a second data server, wherein the second data server implements the second file system, different from the first file system, for managing file access and storage, and wherein the first client is unaware that the second data server implements the second file system;

instructions for causing one or more processors to select a second protocol interpreter from the plurality of different protocol interpreters, wherein the second protocol interpreter implements a second file access protocol which enables interaction with the second file system;

instructions for causing one or more processors to invoke the second protocol interpreter to interact with the second file system of the second data sever to obtain therefrom a second list of contents, wherein the second list of contents sets forth a hierarchical listing of at least a portion of the contents of the second file system on the second data server, the second list of contents comprising one or more directories and zero or more files; and

instructions for causing one or more processors to send at least a portion of the second list of contents to the first client.

47. The computer readable medium of claim 46, wherein the first client does not implement the second file access protocol such that the first client is incapable of interacting directly with the second file system.

48. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a request from a second client to browse contents of a second file system on a second data server, wherein the second data server implements the second file system, different from the first file system, for managing file access and storage, and wherein the second client is unaware that the second data server implements the second file system;

instructions for causing one or more processors to select a second protocol interpreter from the plurality of different protocol interpreters, wherein the second protocol interpreter implements a second file access protocol which enables interaction with the second file system;

instructions for causing one or more processors to invoke the second protocol interpreter to interact with the second file system of the second data sever to obtain therefrom a second list of contents, wherein the second list of contents sets forth a hierarchical listing of at least a portion of the contents of the second file system on the second data server, the second list of contents comprising one or more directories and zero or more files; and

instructions for causing one or more processors to send at least a portion of the second list of contents to the second client.

49. The computer readable medium of claim 48, wherein the second client does not implement the second file access protocol such that the second client is incapable of interacting directly with the second file system.

50. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a request from the first client to further explore a particular directory on the first data server;

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data sever to obtain therefrom a second list of contents, wherein the second list of contents comprises zero or more directories and one or more files stored within the particular directory; and

instructions for causing one or more processors to send at least a portion of the second list of contents to the first client.

51. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a request from the first client to access a particular file stored on the first data server;

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom;

instructions for causing one or more processors to determine a file type for the particular file;

instructions for causing one or more processors to generate a set of encoding information based upon the file type of the particular file, wherein the set of encoding information comprises information for causing the first client to execute a particular type of application to process the particular file; and

instructions for causing one or more processors to send the particular file and the set of encoding information to the first client.

52. The computer readable medium of claim 51, wherein the instructions for causing one or more processors to send the particular file and the set of encoding information comprises:

instructions for causing one or more processors to send the particular file and the set of encoding information as an electronic mail file to the first client.

53. The computer readable medium of claim 52, wherein the electronic mail file comprises Multipurpose Internet Mail Extension (MIME) information.

54. The computer readable medium of claim 51, wherein the instructions for causing one or more processors to determine a file type for the particular file comprises:

instructions for causing one or more processors to determine a file extension for the particular file; and

instructions for causing one or more processors to process the file extension to determine a file type for the particular file.

55. The computer readable medium of claim 54, wherein the instructions for causing one or more processors to process comprises:

instructions for causing one or more processors to determine a Multipurpose Internet Mail Extension (MIME) type for the file extension.

56. The computer readable medium of claim 55, wherein the set of encoding information comprises the MIME type.

57. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a request from the first client to compress a particular file stored on the first data server;

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom;

instructions for causing one or more processors to compress the particular file to derive a compressed version; and

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to store the compressed version onto the first data server.

58. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a request from the first client to send a particular file stored on the first data server to a recipient;

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data server to retrieve the particular file therefrom; and

instructions for causing one or more processors to send the particular file to the recipient without first downloading the particular file to the first client.

59. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a request from the first client to create a new directory on the first data server; and

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to create the new directory on the first data server.

60. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a request from the first client to store a new file onto the first data server;

instructions for causing one or more processors to receive the new file from the first client; and

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to store the new file onto the first data server.

61. The computer readable medium of claim 43, further comprising:

instructions for causing one or more processors to receive a search request from the first client comprising a set of search criteria;

instructions for causing one or more processors to process the set of search criteria to derive one or more search commands;

instructions for causing one or more processors to invoke the first protocol interpreter to interact with the first file system of the first data server to cause the first file system to implement the one or more search commands; and

instructions for causing one or more processors to receive one or more sets of search results from the first file system.

62. The computer readable medium of claim 61, further comprising:

instructions for causing one or more processors to process the one or more sets of search results to derive a processed set of search results; and

instructions for causing one or more processors to send the processed set of search results to the first client.

63. The computer readable medium of claim 61, wherein the set of search criteria comprises a Boolean operation and/or a wild card.