Simultaneously accessing file objects through Web services and file services

• US 20110029487A1
• Filed: 09/28/2010
• Published: 02/03/2011
• Est. Priority Date: 10/24/2007
• Status: Abandoned Application

• Current Assignee: EMC Corporation (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Fridella, Stephen, Dimitrov, Rossen, Oliveira, Fernando, Eaton, Patrick, Angelone, Raymond
• Application Number:
  US12/924,473
• Publication Number:
  US 20110029487A1
• Time in Patent Office: Days
• US Class Current: 707/634
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

Accessing data file objects includes providing a file system interface on a client, where the file system interface allows an application running on the client to make file system calls to access the data file objects. A Web Services interface may also be provided on the client, where the Web Services interface allows an application to access file objects using the Web Services at the same time that file objects are being accessed through the file system interface. The Web Services interface may be a SOAP interface and/or a REST interface. Accessing data file objects may also include providing a direct file object interface on the client, where the direct file object interface allows an application to directly access file objects at the same time that file objects are being accessed using the Web Services interface and using the file system interface.

Claims

1. -22. (canceled)

23. A method of managing objects for a data file, comprising:

obtaining a metadata object for the file;

determining if the metadata object indicates that a portion of the data file includes synchronous mirrors; and

in response to a write of new data to the data file, writing the new data to each synchronous mirror.

24. A method, according to claim 23, wherein data objects of a data file may be in one of four states:

current, stale, empty, and immutable.

25. A method, according to claim 24, wherein, in response to a read operation and the corresponding data object being in a stale state, data is read for a corresponding synchronous mirror that is in a current state.

26. A method, according to claim 23, wherein the metadata is provided through a Web Services interface that includes at least one of:

a SOAP interface and a REST interface.

27. A method, according to claim 23, wherein the metadata is provided through a direct file object interface that allows an application to directly access file objects at the same time that file objects are being accessed using at least one other interface.

28. A method, according to claim 23, further comprising:

providing file name services that translate file names into file object identifiers, wherein the file name services are accessed by at least one of;

a file system interface and a Web Services interface.

29. Computer software, provided in a computer-readable medium, that manages objects for a data file, the software comprising:

executable code that obtains a metadata object for the file;

executable code that determines if the metadata object indicates that a portion of the data file includes synchronous mirrors; and

executable code that writes the new data to each synchronous mirror in response to a write of new data to the data file.

30. Computer software, according to claim 29, wherein data objects of a data file may be in one of four states:

current, stale, empty, and immutable.

31. Computer software, according to claim 30, wherein, in response to a read operation and the corresponding data object being in a stale state, executable code causes data to be read for a corresponding synchronous mirror that is in a current state.

32. Computer software, according to claim 29, wherein the metadata is provided through a Web Services interface that includes at least one of:

a SOAP interface and a REST interface.

33. Computer software, according to claim 29, wherein the metadata is provided through a direct file object interface that allows an application to directly access file objects at the same time that file objects are being accessed using at least one other interface.

34. Computer software, according to claim 29, further comprising:

executable code that provides file name services that translate file names into file object identifiers, wherein the file name services are accessed by at least one of;

a file system interface and a Web Services interface.