System and method for invoking WebDAV methods via non-WebDAV protocols

• US 20040163037A1
• Filed: 02/17/2003
• Published: 08/19/2004
• Est. Priority Date: 02/17/2003
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Friedman, Richard, Kinner, Jason, Snyder, Joseph J.
• Application Number:
  US10/368,700
• Publication Number:
  US 20040163037A1
• Time in Patent Office: Days
• US Class Current: 715/501.1
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

A method for invoking a WebDAV method via a non-WebDAV protocol is provided. The method comprises receiving a request for a WebDAV method via a non-WebDAV protocol, and responsive to receiving the request, invoking the requested WebDAV method. A system for invoking a WebDAV method via a non-WebDAV protocol is provided. The system comprises a means for receiving a request for a WebDAV method from a client via a non-WebDAV protocol, and a means for invoking the requested WebDAV method responsive to a received request.

Claims

1. A method for invoking a WebDAV method via a non-WebDAV protocol, the method comprising:

receiving a request for a WebDAV method via a non-WebDAV protocol; and

responsive to receiving said request, invoking the requested WebDAV method.

2. The method of claim 1 further comprising:

translating the received request to a WebDAV protocol.

3. The method of claim 2 wherein said invoking comprises:

communicating the translated request via said WebDAV protocol to a WebDAV method processing unit.

4. The method of claim 1 further comprising:

translating the received request to a canonical format.

5. The method of claim 4 further comprising:

translating the canonical formatted request to a WebDAV protocol.

6. The method of claim 1 wherein said receiving comprises:

receiving said request via any of a plurality of different non-WebDAV protocols.

7. The method of claim 6 further comprising:

determining to which of a plurality of different input handlers to communicate the received request;

communicating the received request to a determined one of said plurality of different input handlers; and

said determined one of said plurality of different input handlers translating said received request to a canonical format.

8. The method of claim 7 further comprising:

communicating said canonical formatted request to a request executor; and

said request executor translating said canonical formatted request to a WebDAV protocol and communicating the request via said WebDAV protocol to a WebDAV method processing unit.

9. The method of claim 6 wherein said plurality of different non-WebDAV protocols comprises at least one selected from the group consisting of:

File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), Simple Object Access Protocol (SOAP), Enterprise Java Beans (EJB), Component Object Model (COM), and Distributed Component Object Model (DCOM).

10. The method of claim 6 wherein said plurality of different non-WebDAV protocols comprises at least one communication protocol that does not natively support WebDAV methods.

11. The method of claim 10 wherein said at least one communication protocol that does not natively support WebDAV methods comprises at least one selected from the group consisting of:

File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), and Simple Object Access Protocol (SOAP).

12. The method of claim 6 wherein said plurality of different non-WebDAV protocols comprises at least one component technology.

13. The method of claim 12 wherein said at least one component technology comprises at least one selected from the group consisting of:

Enterprise Java Beans (EJB), Component Object Model (COM), and Distributed Component Object Model (DCOM).

14. The method of claim 6 wherein said plurality of different non-WebDAV protocols comprises at least one communication protocol that does not natively support WebDAV methods and at least one component technology.

15. A system for invoking a WebDAV method via a non-WebDAV protocol, the system comprising:

means for receiving a request for a WebDAV method from a client via a non-WebDAV protocol; and

means for invoking the requested WebDAV method responsive to a received request.

16. The system of claim 15 further comprising:

means for translating a received request from said non-WebDAV protocol to a WebDAV protocol.

17. The system of claim 15 wherein said means for receiving comprises:

means for receiving a request via any of a plurality of different non-WebDAV protocols.

18. The system of claim 17 further comprising:

a plurality of translating means each for translating a received request from a particular non-WebDAV protocol to a canonical format.

19. The system of claim 18 further comprising:

means for determining which of said plurality of translating means to communicate a received request.

20. The system of claim 18 further comprising:

means for translating a canonical formatted request to a WebDAV protocol request.

21. A bridge for enabling invocation of a WebDAV method via a non-WebDAV protocol, the bridge comprising:

receiver operable to receive a request for a WebDAV method from a client via a non-WebDAV protocol;

input handler operable to translate a received request from any of a plurality of different non-WebDAV protocols to a canonical format; and

request executor operable to translate a canonical formatted request to a WebDAV protocol request for invoking a requested WebDAV method.

22. The bridge of claim 21 wherein said plurality of different non-WebDAV protocols comprises at least one selected from the group consisting of:

File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), Simple Object Access Protocol (SOAP), Enterprise Java Beans (EJB), Component Object Model (COM), and Distributed Component Object Model (DCOM).

23. The bridge of claim 21 wherein said canonical format comprises a table.

24. The bridge of claim 21 wherein said bridge comprises a plurality of receivers, each of said plurality of receivers operable to receive a request for a WebDAV method from a client via a different non-WebDAV protocol.

25. Computer-executable software code stored to a computer-readable medium, said computer-executable software code comprising:

code for translating a request for a WebDAV method from a non-WebDAV protocol to a WebDAV protocol; and

code for invoking the requested WebDAV method via said WebDAV protocol.

26. The computer-executable software code of claim 25 wherein said code for translating further comprises:

code for translating said request to a canonical format.

27. The computer-executable software code of claim 26 wherein said code for translating said request for a WebDAV method from a non-WebDAV protocol to a WebDAV protocol further comprises:

code for translating the canonical formatted request to a WebDAV protocol.

28. The computer-executable software code of claim 25 further comprising:

code for receiving said request via any of a plurality of different non-WebDAV protocols.

29. The computer-executable software code of claim 28 further comprising:

code for determining to which of a plurality of different input handlers to communicate the received request;

code for communicating the received request to a determined one of said plurality of different input handlers; and

said determined one of said plurality of different input handlers comprising code for translating said received request to a canonical format.

30. The computer-executable software code of claim 29 further comprising:

code for communicating said canonical formatted request to a request executor; and

said request executor comprising code for translating said canonical formatted request to said WebDAV protocol.

31. The computer-executable software code of claim 28 wherein said plurality of different non-WebDAV protocols comprises at least one selected from the group consisting of:

File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), Simple Object Access Protocol (SOAP), Enterprise Java Beans (EJB), Component Object Model (COM), and Distributed Component Object Model (DCOM).

32. The computer-executable software code of claim 28 wherein said plurality of different non-WebDAV protocols comprises at least one communication protocol that does not natively support WebDAV methods and at least one component technology.