METHOD AND SYSTEM FOR PLATFORM-INDEPENDENT FILE SYSTEM INTERACTION

• US 20100146493A1
• Filed: 02/10/2010
• Published: 06/10/2010
• Est. Priority Date: 12/21/2000
• Status: Active Grant

• Current Assignee: Ip Ot Sub Ulc
• Original Assignee: Open TEXT SA (Open Text Corporation)
• Inventors: White, Eric
• Granted Patent: US 8,079,024 B2
• Time in Patent Office: Days
• US Class Current: 717/140
• CPC Class Codes: G06F 16/164 File meta data generation
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Embodiments disclosed can provide a simple, singular programmatic interface for application developers to access and manipulate ASCII and non-ASCII file specifications in a cross-platform development environment regardless of operating system encoding capabilities or of the nature of the original file specification encoding. An application development environment is configured on a computer system such that a magic class file string object is instantiated when a bit string of a first encoding is received. The bit string represents a file specification of a file containing application code written by an application developer. The magic class file string object automatically determines what target operating system is being called by a function call in the application code, automatically transcodes the bit string from the first encoding into a second encoding of the target operating system, and automatically makes a correct file system API call specific to the target operating system.

Claims

1. A method for accessing and manipulating file specifications in a cross-platform development environment, comprising:

configuring an application development environment on a computer system to instantiate a magic class file string object when a bit string of a first encoding is received, wherein the bit string represents a file specification of a file, wherein the file contains application code, and wherein the application code comprises a function call;

automatically determining a target operating system that is being called by the function call, wherein the magic class file string object performs the automatic determining;

automatically transcoding the bit string of the first encoding into a second encoding of the target operating system, wherein the magic class file string object performs the automatic transcoding; and

automatically making a file system application program interface (API) call specific to the target operating system, wherein the magic class file string object performs the automatic API call.

2. The method according to claim 1, wherein the file specifications include American Standard Code for Information Interchange (ASCII) encoded file specifications and non-ASCII encoded file specifications.

3. The method according to claim 1, wherein the automatically determining further comprises automatically determining the target operating system'"'"'s file system API capabilities.

4. The method according to claim 1, further comprising:

forwarding the magic class file string object to the target operating system'"'"'s file system to initiate a write to disk when the file associated with the bit string is to be written to disk.

5. The method according to claim 1, wherein the magic class file string object contains pieces of code programmed to make one or more automatic determinations at compile time.

6. The method according to claim 5, wherein the pieces of code comprise a set of conditional logic for determining which one or more file system specific API calls are to make.

7. The method according to claim 5, wherein the pieces of code comprise an instruction for turning on at compile time a switch to link to a library through which all system input/output requests are processed.

8. A computer program product comprising at least one computer readable storage medium storing instructions translatable by a processor to perform:

instantiating a magic class file string object when a bit string of a first encoding is received in an application development environment running on a computer system, wherein the bit string represents a file specification of a file, wherein the file contains application code, and wherein the application code comprises a function call;

automatically determining a target operating system that is being called by the function call;

automatically transcoding the bit string of the first encoding into a second encoding of the target operating system; and

automatically making a file system application program interface (API) call specific to the target operating system.

9. The computer program product of claim 8, wherein the file specifications include American Standard Code for Information Interchange (ASCII) encoded file specifications and non-ASCII encoded file specifications.

10. The computer program product of claim 8, wherein the instructions are further translatable by the processor to automatically determine the target operating system'"'"'s file system API capabilities.

11. The computer program product of claim 8, wherein the instructions are further translatable by the processor to forward the magic class file string object to the target operating system'"'"'s file system to initiate a write to disk when the file associated with the bit string is to be written to disk.

12. The computer program product of claim 8, wherein the magic class file string object contains pieces of code programmed to make one or more automatic determinations at compile time.

13. The computer program product of claim 12, wherein the pieces of code comprise a set of conditional logic for determining which one or more file system specific API calls are to make.

14. The computer program product of claim 12, wherein the pieces of code comprise an instruction for turning on at compile time a switch to link to a library through which all system input/output requests are processed.

15. A system, comprising:

a computer system running an application development environment and having at least one computer readable storage medium and a processor, wherein the at least one computer readable storage medium stores instructions translatable by the processor to perform;

instantiating a magic class file string object when a bit string of a first encoding is received in the application development environment, wherein the bit string represents a file specification of a file, wherein the file contains application code, and wherein the application code comprises a function call;

automatically determining a target operating system that is being called by the function call;

automatically transcoding the bit string of the first encoding into a second encoding of the target operating system; and

automatically making a file system application program interface (API) call specific to the target operating system.

16. The system of claim 15, wherein the file specifications include American Standard Code for Information Interchange (ASCII) encoded file specifications and non-ASCII encoded file specifications.

17. The system of claim 15, wherein the instructions are further translatable by the processor to automatically determine the target operating system'"'"'s file system API capabilities.

18. The system of claim 15, wherein the instructions are further translatable by the processor to forward the magic class file string object to the target operating system'"'"'s file system to initiate a write to disk when the file associated with the bit string is to be written to disk.

19. The system of claim 15, wherein the instructions comprise a set of conditional logic for determining which one or more file system specific API calls are to make.

20. The system of claim 15, wherein the instructions comprise an instruction for turning on at compile time a switch to link to a library through which all system input/output requests are processed.