TWI399693B - File system refresented inside a database - Google Patents

Abstract

The subject invention provides a system and/or a method that facilitates adapting at least two disparate file systems. A file system adapter can provide uniformity and/or seamless integration between a first file system and a second file system. The file system adapter can employ a file-backed item that is enriched by a file to provide at least one of a property to an item and a file stream associated with the item. The file-backed item can allow a manipulation by at least one of an API for the first file system and an API for the second file system.

Description

File system presented in the database

The present invention relates to a database, and more particularly to a file system presented in a database.

Various developments in computer technology (such as microprocessor speed, memory capacity, data transmission bandwidth, software functions, and the like) have been widely used to increase the use of computers in various industries. Such a powerful server system (usually constructed as a server array) is often used to provide service requirements from external sources such as the World Wide Web.

As the number of useful electronic materials increases, it becomes more important to store such data in a manageable manner that facilitates the user's convenient and rapid search and retrieval of data. Today, a common method is to store electronic data in one or more databases. In general, for example, a typical database can be referred to as an informational organization collection with one of the data architectures, which is a computer program that can quickly search for and select the desired data segments to structure. Typically, data within a database is constructed in one or more tables. Such a table is organized into an array of rows and columns.

Furthermore, the form can be composed of a set of records, and a record contains a set of fields. Records are usually referred to as columns in a table, and are usually referred to as rows in the record field. Such an index row group can refer to a particular data in a table. For example, a column can store a complete record of information about a sale, a person, or a plan. Similarly, the rows of the table may define a scatter portion of a column having the same general data format, where the row may define the fields of the record.

Each separate piece of material is usually not very useful. Database applications make data more useful because they help users organize and process data. The database application allows the user to compare, sort, organize, merge, detach, and link the data so that useful information can be generated from the material. However, the capacity and functionality of the database has grown to an astonishing amount, and the database storage capacity can be used endlessly. In addition, a typical database system provides limited query capabilities based on time, file extension, location and size. For example, in order to search a large amount of data related to a database, a typical search is limited to a file name, a file size, and a creation date, wherein such techniques are disadvantageous and inappropriate.

As the continuous increase in data from end users has reached a peak around the problems and difficulties in discovering, connecting and storing such data. End users write files, store photos, retrieve music from discs, receive emails, keep a backup of emails, and more. For example, in a simple step of producing a music disc, an end user can create millions of bits of data. Information is required to capture music from a disc, convert files to an appropriate format, create a disc cover, and design a disc label.

Not only does the complexity plague the user, but the developer has similar problems with the data. Developers create and write a variety of applications, modifying personal applications to a highly developed enterprise application. When creating and/or developing, developers collect data frequently, if not at any time. When such information is obtained, it needs to be stored. In other words, the developer and the end user are jeopardized by problems and difficulties in discovering, connecting, and storing data.

Moreover, technological advances in the database have led to many formats and/or configurations. The format and/or configuration of the database has been appropriately increased, and such changes can make integration difficult. In other words, different archive databases are typically not suitable for each other based on development differences. Therefore, the disadvantages associated with conventional systems and databases of the above examples must be overcome.

BRIEF DESCRIPTION OF THE DRAWINGS The following presents a simplified summary of the invention in order to provide a This summary is not an extensive overview of the invention. The key or critical elements of the invention and the scope of the invention are not intended to be determined herein. The sole purpose is to provide some of the concepts of the present invention in a simplified form as a

The present invention is directed to systems and/or methods that facilitate adaptation to different file systems. A file system adapter provides consistency between a first file system and a second file system. The consistency may allow for an application and/or application interface (API) for the first file system to be built in the second file system. The file system adapter can create a file backup item that can be an option associated with the second file system that relies on a file and/or a file stream to convey at least one associated feature. The file backup item can utilize the file and/or associated file stream and features and/or pass the item along with the metadata in the second file system. By utilizing the file backup item, the file system adapter is allowed to operate as follows: the application interface associated with the second file system; and an existing application associated with the existing and previous versions of the first file system interface. The file system adapter can also provide synchronization between the first file system and the second file system. It should be understood that the file backup item may incorporate the characteristics of the first file system into the second file system, such as but not limited to: an attribute, a security feature, a file stream, a file, and the like.

According to one aspect of the invention, the file system adapter can include an attribute element. The attributes provided by the attribute element are related to a file and/or file stream that is associated with the first file system to the second file system. A file may have at least one attribute such as, but not limited to, read only, compressed, archived archives, etc., where a single element and/or a byte may represent such attributes. The attribute element may allow the file backup item representing a file and or file stream in the first file system to include such attributes in the second file system.

In accordance with another aspect of the present invention, the file system adapter can include a relay data processing component that allows at least one characteristic to be synchronized between the item, the file backup item, and a backup file (eg, , in the file system, the file represented by the file backup project). A feature may be modified in the backup file stream, wherein the relay data processing component may raise a new value for the appropriate form of the item within the second file system. In addition, a feature can be changed via an application interface associated with the second file system; the relay data processing component can downgrade the new file value of the backup file stream in the first file system.

In accordance with another aspect of the present invention, the file system adapter can include a pair of "backup" (ghost) components that provide synchronization for one of the file backup items. Additionally, a property channel element can be used to provide attribute tunneling to facilitate file name changes and/or resources stored within the second file system. Additionally, the file system adapter can include a directed loopless map (DAG) component that incorporates the present invention using a directed acyclic graph. In other aspects of the invention, several methods are proposed to be applicable to different file systems.

Some exemplary embodiments of the invention are described in detail in the following description and appended drawings. However, these aspects are only a few of the many ways in which the principles of the invention can be applied, and the invention is intended to include all aspects and equivalents thereof. Other advantages and novel features of the present invention will become apparent from the Detailed Description and Description of the Drawing.

For example, as used in this application, the terms "component", "system", "interface" and the like mean a computer-related entity, or hardware, software (for example, in terms of execution) and/or firmware. . For example, an element can be a program built into a processor, a processor, an object, an implement, a program, and/or a computer. For example, an application executing on a server and the server can be an element. One or more components can reside within a single program and a component can be located in a computer and/or distributed between two or more computers.

Referring to the drawings, the same reference numerals are used to refer to the same elements. In the following description, numerous specific examples are set forth to provide a However, it is apparent that the present invention may be applied to these specific examples, and in other instances, the structures and devices are presented in the form of block diagrams for describing the present invention.

Referring now to the drawings, FIG. 1 illustrates a system 100 that facilitates the transfer of a file system to a different file system. A file system 102 can be a file storage system in which the structure is based on a file stream and/or a directory. The file system 102 can utilize the file stream to enable an application and/or application interface (API) to supplement the file stream to provide more structure. A file system 104 can be a more complex model in which an item, a sub-item, a feature, and a dependency are defined to allow a message within the file system 104 to be represented as a complex form of an instance. An option can be defined as the smallest compatible unit in the file system 104, which can be independently protected, concatenated, synchronized, copied, backed up/restored, and the like. The project is a form of entity in which all items in the file system 104 can be stored in a single universe of a project. The file system 104 can be based on at least one item and/or a storage structure. The file system 104 can be a storage platform that exposes a large amount of relay material stored in the archive as a project. It should be understood that the file system 104 can be a file storage system represented by a data model to support the functions described.

A file system adapter 106 can provide compatibility and/or consistency between the file system 102 and the file system 104. This compatibility and/or consistency may allow an application and/or an API for the file system 102 to be deployed in the file system 104. The file system adapter 106 can deploy a file backup item, which can be an item associated with the file system 104, which relies on a file and/or a file stream to convey at least one associated feature. The file backup project can act as a bridge between the file system 102 and the fully systemized file system 104 and/or a data schema associated therewith. For example, an image item in the file system 104 can be a file backup item, wherein the image item is backed up by a file conforming to a standard image format (eg, JPEG, TIF, BMP, etc.) of the file system 102. . In other words, the file backup item can utilize the file and/or associated file stream (e.g., utilized by the file system 102) to communicate the item with attendant features and/or relayed material in the file system 104. By utilizing the file backup item, the file system adapter 106 can operate as follows: an API associated with the file system 104; and an existing application interface associated with existing and previous versions of the first file system. The file system adapter 106 can provide synchronization between the file system 102 and the file system 104. In particular, the information provided by the file backup project can be synchronized with the corresponding data in the backup file. It should be understood that the file backup item may provide the file system 104 with the characteristics of the file system 102, such as but not limited to: an attribute, a security feature, a file stream, a file, and the like.

The system 100 further includes an interface component 108 that provides a number of adapters, connectors, channels, communication paths, and the like to integrate the file system adapter 106 to all of the actual operating systems. In addition, the interface component 108 can provide a variety of adapters, connectors, channels, communication paths, and the like for interacting with the data and file system adapter 106. It should be understood that although the interface component 108 is incorporated into the file system adapter 106, the manner of deployment is not limited in this respect. For example, interface component 108 can be a separate component for receiving or transmitting data associated with system 100.

Figure 2 illustrates a system 200 for transferring at least two different file systems to provide consistency. A file system adapter 206 can provide consistency and/or compatibility between a file system 202 and a file system 204. However, it should be understood that the file system adapter 206 can be used to transfer a plurality of different file systems. The file system 202 can be a file stream and a catalog file system utilizing at least one API and/or application. For example, the API and/or applications associated with the file system 202 can be, but are not limited to, a 16-bit, 32-bit, etc. version. The file system 204 can be a composite structure that utilizes an item as a consistency unit, wherein the relay material, characteristics, and relevance are deployed as a composite style entity. The file system 204 can be a data model that can describe the shape of the data, declare restrictions to indicate some semantic consistency of the material, and define semantic relevance among the data. Applications utilizing the file system adapter 206, the application interface, and/or associated with the file system 202 can be utilized consistently within the file system 204. It should be understood that the file system 202, the file system 204, and the file system adapter 206 are substantially similar to the file system 102, file system 104, and file system adapter 106 of FIG. 1, respectively.

The file system adapter 206 can include an analysis component 210 that analyzes the file system 202. The analysis component 210 can determine the directory and/or files associated therewith to facilitate providing a system that can be transferred to and/or compatible with the file system 204. The analysis component 210 can determine at least one leaf node. It should be understood that a leaf node may be represented as a file backup item, and files of all directory and/or file system 202 may be represented as items of file system 204. Thus, directories and/or files that are not leaf nodes are presented in the file system 204, but there are no streams associated therewith.

The file system adapter 206 further includes a generating component 212 that creates and/or generates a file backup item. The generating component 212 can create the file backup item based at least in part on the analysis of the file system 202. For example, the generating component 212 can create a file backup project for any leaf node associated with the file system 202, wherein the backup project is supplemented by a file and/or file stream from the file system 202, The file backup item is compatible with the file system 204. The generating component 212 can create a file backup item by using at least one of the following: the file backup item has a related (eg, backup) file stream; the file backup item cannot contain other items (eg, they are tied to a leaf node in a namespace) The file backup project can be backed up and restored (see below); and a file attribute (see below) is maintained for the file backup item.

The file backup project can act as a bridge between the file system 202 and the file system 204. An item of any file system 204 may be referred to as a file backup item, if (1) at least a portion of the content is from a file system and/or a file stream of the file system 202, and/or (2) one of the active files is at least One of the file system related APIs and/or applications. The file backup item in the file system 204 can store a relay data feature associated with a project, and can also store a file stream associated with the project. It should be understood that the file system 202 folder/directory/archive hierarchy mechanism can be presented in the file system 204 using include items that include other items, including file backup items. Therefore, an application utilizing the file system 202 application interface can function perfectly with the storage mechanism of the file system 204.

Figure 3 is a diagram showing a system 300 for transferring a file stream related file system and a relay data related file system. A file system adapter 306 can provide consistent and/or compatible interaction between a file system 302 and a different file system 304. The file system adapter 306 can utilize a file backup item as an item in the file system 304 to communicate at least one characteristic and/or relay data with a file and/or a file stream associated with the file system 302. . The file backup project can act as a bridge between the file system 302 (eg, format) and the file system 304 (eg, a composite system of fully systemized entities).

The file system adapter 306 can include an attribute component 310 that provides file system 304 with attributes associated with the file and/or file streams associated with the file system 302. For example, file system 302 utilizes a file stream storage system in which a file can have at least one attribute, such as but not limited to: read only, compressed, categorized files, etc., where one bit and/or bit Tuples can represent such attributes. The attribute element 310 can allow a file backup item representing a file and/or a file stream in the file system 302 to incorporate such attributes into the file system 304. It should be understood that the attribute element 310 can be represented by a respective file backup item and/or corresponding to such attributes as a characteristic. In an example, attribute element 310 may provide an update to an archive attribute when the file stream via a call from file system 302 ends. This feature can be updated by an API associated with the file system 304 (described below).

The attribute element 310 can further provide an item attribute, which is a nested version that can include all items common attributes. This attribute can be set by any application that operates via the file system 304 and/or an API associated with the file system 304. The attributes provided below may be used as an example of an application and/or a user of the file system 302.

The file system switch 306 includes a relay data processor component 312 that allows at least one feature to be synchronized between the project, the file backup item, and a backup file (e.g., in the file system 302 for the file backup item) Representation file). For example, a feature can be modified in the backing file stream, wherein the relay data processor component 312 can raise a new value for the appropriate field of the internal file of the file system 304. In another example, a feature can be changed by an API associated with the file system 304; the relay data processor component 312 can downgrade the new file value to the backup file stream in the file system 302. It should be understood that a different form of file backup item may have a distinct relay data processor element 312 associated therewith.

For example, a non-synchronized promotion can be achieved by the relay data processor component 312 after a file is closed by the application. On the other hand, the demotion can also be asynchronous. A special project feature clearly indicates whether the upgrade feature is synchronized between a project and the backup file. The state of a rise can clearly indicate the error state of a project. The setting of this state may not be synchronized to a file ending with the system preset stream of the file backup item. This state can be a null value (NULL) for a non-archive backing item. The following table describes the possible values for a boosted state.

It should be understood that the file system 306 can utilize a project form in which at least one item and/or file backup item is stored. The project form may utilize a file stream form and/or a file attribute form associated with a file stream and/or a file attribute to a respective file backup item that may be stored in the item form. For items to be used as a file backup item, the file stream table and/or the file attribute table may store the respective file stream and the file attributes of the file (eg, include the file stream and/or file to supplement and/or Or pass at least one feature). It should be understood that the file attributes can be stored in a project form. The archive attribute semantics can be performed by, for example, an update API.

Furthermore, the global project form may include the following additions to a file backup project.

For example, the file stream table can have the following characteristics.

The following is an example of a file system utilizing a file stream storage in which a 32 bit system is used but is not considered to be a limitation of the present invention. The following is an example of the attributes of a 32-bit file system that can be supported by system 300 and a file storage system (FSS) (e.g., file system 304).

Continuing with the previous examples, the following attributes can be partially supported and/or fully supported.

Figure 4 illustrates a system 400 for transferring and/or combining a file system to a distinct file system. A file system adapter 406 can provide consistency between a file system 402 and a file system 406. The file system 402 can be based on a file stream and includes a directory, a folder, and a file. For example, the file system 402 can be a 16-bit file system, a 32-bit file system (eg, a FAT file system.), where the API (eg, a 16-bit API, a 32-bit API). Use such file systems in their respective operating systems. The file system 404 can be a composite type system and includes a type, a project, a feature, a correlation, a type of example, a storage, and the like. It should be understood that the file system 404 indicates that the information unit is an item related to the relay material and/or characteristics. Moreover, the file system 402 and the file system 404 can be substantially similar to the file systems 302, 304, 202, 204, 102, and 104 in Figures 3, 2, and 1 respectively.

The file system adapter 406 can create a file backup item based on at least the file structure of the file system 402 for perfect integration into the file system 404. The file backup item may be passed and/or supplemented for a file and/or a file stream to create and/or attach attributes utilized by the file system 404. Because the file backup item is of a type having the file and/or its associated file stream, the file backup item may allow an API for the file system 402 to be utilized in the file system 404 regardless of whether the API format is The file is required to be streamed. In other words, the file backup project is a bridge between the file system 402 and the file system 404.

The file system adapter 406 can include a pair of backup storage restore elements 410 that provide synchronization to one of the file backup items. The backup restore component 410 can create a backup restore project that is a copy of the other file backup project but does not include the file stream. Moreover, the backup and restore component 410 can provide a backup, which is an operation for establishing a backup restore project and/or converting a presence project to a backed up restore project. The backup restore component 410 can also provide an unghosting operation that transforms a backup restore project into a standard project. While the backup restore component 410 is coupled to the file system adapter, it should be understood that the backup restore component 410 can be a separate component, and/or a separate unit.

The following table provides a further description of the functionality of backup restore component 410.

In an example, the backup restore component 410 can back up an entity for the file system 404 backup. If the project is not a file backup project, an "error" is returned. If the project has been backed up and restored, the operation is a network active open source operation (noop) and responds with a "success". The backup restore component 410 can propagate the information to all of the secondary entities (eg, all embedded items, relationships, and/or extensions) within the backed up restored project tree structure and set a one-digit "true" to inform the entity The item status has been backed up and restored. After the backup restore occurs, the file stream content can be deleted for the backup restore project (for example, it sets the file stream to NULL.).

In another example, an entity may back up (unghost) the backup resource element 410. If the project is not a file backup project, respond to a "wrong". If the project has not been backed up and restored, the operation is a network active open source operation (noop) and returns a "success". A single element can be set to "pseudo" to inform the entity that the entity item has not been backed up and restored. Create a zero-length file stream and add it to a file stream table. The reverse backup restore does not restore the archive stream content, and a pager must explicitly pass the file stream with the appropriate content (eg, preferably in approximately the same process). In an example, the types of usage for the back-up backup operation may be: open processing; reverse backup restore project; pass/restore archive stream content; and commit processing.

The file system switch 406 can include an attribute tunneling element (ATC) 412. The ATC 412 provides attribute tunneling to facilitate name changes and/or to convert resources within the file system. The file system 402 utilizes a temporary file that is created when opened, accessed, and or edited. When the file is stored in the file system 402, the temporary file and the stored file name are swapped. For example, a file food.doc can be created and accessed in the file system 402. When accessed within the file system 402, the file f1.tmp can be created. The food.doc can be moved to f2.tmp, where f1.tmp is moved to food.doc. The file f2.tmp can then be deleted in the file system 402. However, based on the file system 404 structure and an item used to represent the information unit, an API call for updating one of the names is an expensive resource. In general, ATC 412 allows swapping of related file streams between two file backup items. For example, a file stream stored in a form file stream table can be utilized by the ATC 412, wherein the item IDs of the two file streams can be exchanged. Although described in conjunction with the file system adapter 406, it should be understood that the ATC 412 can be a separate component, incorporated into any suitable component, and/or combinations thereof.

Figure 5 illustrates a file backup project established to facilitate the transfer of multiple distinct file systems. In particular, a file backup item 502 can provide consistency between a file system 504 and a file system 506. It should be understood that file system 504 can be substantially similar to file systems 402, 302, 202, and 102, respectively, in Figures 4, 3, 2, and 1. Moreover, the file system 506 can be substantially similar to the file systems 404, 304, 204, and 104 of Figures 4, 3, 2, and 1 respectively.

The file backup item 502 can provide a semantic layer 508 that provides semantics (eg, for an update API, and/or one of the aforementioned relay data processor elements). The file backup item 502 also includes a file stream 510. The file stream 510 can have the technology of the file system 504. An application associated with the file system 504 (eg, a 32-bit application and/or application interface) can utilize the file backup item 502 to directly manipulate the file stream of the file stored in the file system 506. The techniques of many file systems 504 (such as, but not limited to, cache management, streaming, byte range locking, and memory mapping) need not be re-deployed by file system 506. The current streaming system is associated with the file backup item 502. Moreover, the file stream 510 can be protected by at least one access control list (ACL). The file stream 510 can be represented by a file stream table, such as the following table.

In addition, the file backup item 502 can also include an archive attribute 512, a physical item status 514, a change unit 516, and a project profile 518. The archive attribute 512 can be stored in a project form, wherein the archive attribute semantics can be deployed (eg, an update API). The entity item status 514 can have attributes stored in a physical item status item user defined version (UDT) field. The semantics of the entity item status attribute can be deployed for the update API and/or the relay data processor element (not shown). Additionally, the file backup item 502 can utilize the change unit 516 to change at least one unit and/or project material 518 that represents material associated with an item.

In an example, the following table may represent features of at least one physical item state 514.

Figure 6 illustrates a system 600 for facilitating the transfer of a file stream associated with a file system and a file system related relay data. A file system adapter 606 can provide consistency and/or perfect integration into a file system 602 (eg, a file streaming system utilizing a 32-bit application interface) and a file system 604 (eg, utilizing a project) , a type, an attribute and a related object to represent the data unit of the data unit). It should be understood that the file system 602 can be substantially similar to the file systems 504, 402, 302, 202, and 102 of Figures 5, 4, 3, 2, and 1 respectively. Moreover, the file system 604 can be substantially similar to the file systems 506, 404, 304, 204, and 104 of Figures 5, 4, 3, 2, and 1 respectively.

A directed no cycle diagram (DAG) element 608 can be used in conjunction with the present invention. The DAG element 608 can utilize a directed graph without any loops, where for any vertex there is no directional starting and ending point of the vertices. When a sink is at the apex of an outward boundary, a source has no vertices into the boundary. A limited DAG has at least one source and at least one slot. The length of a DAG is (for example, the number of boundaries of a longest directional path). It should be understood that when the file system 604 can utilize the DAG component 608 by the file system adapter 606, the file system 602 does not incorporate a DAG. Although described as a separate unit, the DAG component 608 can be coupled to the file system adapter 606 and/or any other suitable component. By utilizing the DAG component 608, a file can simultaneously describe the two directories. For example, when a file is deleted from a directory and completely removed, the file can still belong to the directory.

Figure 7 illustrates a smart application to facilitate the transfer of a file system to one of the systems 700 of a different file system. The system 700 can include a file system 702, a file system 704, a file system adapter 706, and an interface 108 that can be similar to the various components represented by the previous figures. The system 700 further includes a smart component 708. The smart component 708 can be used by the file system adapter 706 to facilitate the transfer of at least two different file systems. For example, the smart component can be used to facilitate determining the file structure of the file system 702.

It will be appreciated that the smart component 708 can provide an inference or inferred state to the system, environment, and/or user from a group observation by intercepting a recorded event and/or material. For example, Inference can be used to identify a particular condition or action, or can generate a state probability distribution. This inference is probable - that is, the calculation of a probability distribution based on the desired state of the data and object considerations. Inference can also be related to techniques for combining higher-order events from a set of things and/or materials. This inference leads to the construction of a new event or action based on a set of observed events and/or stored event data, whether the event is transiently highly correlated, and whether the event and data are from one or more events and sources of information. Several types of structures (directly or indirectly trained) structures and/or systems (eg, support vector mechanisms, neural networks, expert systems, Bayesian networks, fuzzy logic, data fusion engines...) can be combined with Automated mechanisms and steps referred to in the present invention.

A classifier is a function that maps an input attribute vector (x = (x1, x2, x3, x4, xn)) to the secret category to which the input belongs, that is f(x) = confidence(class). This classification may use a probabilistic and/or statistical analysis (eg, factoring into analysis terms and costs) to predict or infer that a user requires an action to be performed automatically. A support vector machine (SVM) is an example of an application classifier. The operation of the SVM is based on the discovery of a hypersurface in the space of possible inputs that attempts to distinguish trigger criteria from non-triggering events. Intuitively, this makes the classification of test materials that are similar but not identical to the training materials correct. Other directed and undirected model classification methods can be used, including, for example, natural Bayesian, Bayesian networks, decision trees, neural networks, fuzzy logic models, and possible hierarchical models that provide different types of independence. The classification used here also includes statistical regression, which is used to develop a model of prioritization.

A display component 710 can provide several user interface formats to facilitate interaction between a user and any components coupled to the file system adapter 706. As noted above, the display element 710 is an individual entity item that can be used by the file system adapter 706. However, it should be understood that the display element 710 and/or similar display elements can be coupled to the file system adapter 706 and/or a separate unit. The display component 710 can provide one or more graphical user interfaces (GUIs), a command line interface, and the like. For example, a GUI can be presented to provide a user-area or manner to load, input, read material, etc., and can include an area to present such results. These areas can contain known text and/or image areas, including: dialog boxes, static controls, drop-down menus, list boxes, pop-up menus, class editing controls, compound boxes, radio buttons, multi-select buttons, buttons, and graphs. Like a button. In addition, vertical or horizontal reel strips suitable for presenting such navigation and toolbox buttons can be used to determine if an area is viewable. For example, a user can interact with one or more components coupled to the file system adapter 706.

The user can also interact with the above-mentioned areas to select and provide information by various means such as a mouse, a rolling ball, a small keyboard, a keyboard, a stroke and or, for example, sound activation. Typically, a mechanism such as a button or an input button on a keyboard can be used to sequentially enter information for initiating a search. However, it should be understood that the invention is not limited thereto. For example, just highlighting a multi-select button can begin the communication of information. In another example, a command line interface can be used. For example, the command line interface can prompt user information by providing a text message (eg, via a text message on a display and a tone). The user can then provide appropriate information, such as a digital input that provides a choice in the interface prompt or an answer to one of the questions raised in the prompt. It should be understood that the command line interface can be used to connect a GUI and/or API. In addition, the command line interface can be used to connect hardware (eg, video cards) and/or displays (eg, black and white and EGA) with limited graphics support and/or low frequency wide communication channels.

Figures 8 through 10 illustrate the method in accordance with the present invention. For ease of explanation, the method is described in a series of actions. It is to be understood that the invention is not limited to the illustrated acts and/or sequences of the acts, such as acts may occur in various sequences and/or concurrently, and other acts are not presented and described herein. Moreover, the method according to the invention does not require the use of all illustrated acts. Moreover, those skilled in the art will appreciate that the method can represent a series of related states by a state diagram or event.

Figure 8 illustrates a method 800 for facilitating transfer and/or providing consistency between at least two different file systems. A first file system can be a file storage system, wherein the structure is based on a file stream and or a directory. The first file system can utilize the file stream such that an application and/or API can supplement the file stream to provide more structure. A second file system can be a more complex model in which an item, a sub-item, an attribute, and a correlation are defined to represent that the information in the second file system is an instance of the composite model. An item can be defined as the smallest unit of consistency in the second file system, which can be independently protected, serialized, synchronized, copied, backed up/stored, and the like. The project is a type of entity in which all items in the second file system can be stored in a single global scope of the project. The second file system can be based on at least one item and or a storage structure. The second file system can be a storage platform that exposes a large amount of relay data stored in the file in a project type.

At component symbol 802, a first file system based on the file stream can be analyzed. Such analysis can determine the file structure and its content can be used to provide consistency. At component symbol 804, a file backup item can be created based at least on the analysis. For example, the analysis can determine the number of a 32-bit archive storage system and the number of leaf nodes associated with the structure. Thus, when an item is used to represent a file and/or directory of a non-leaf node, the file backup item can be generated for each leaf node associated with the first file system. The file backup item can be an item located within the second file system that relies on a file and/or file stream to convey some or all of its characteristics. The file backup project can act as a bridge between the first file system and the second file system. At component symbol 806, the file backup item can be used to provide consistency between two distinct file systems, at least to a degree that at least utilizes the first file system utilizing a file stream and a file, and the combined inclusion and first file The second file system of the system-related file and/or file backup project of the file stream.

Figure 9 illustrates a method 900 for transferring a file system to a distinct file system. At component symbol 902, a first file system utilizing a file and/or a file stream as its structure is analyzed. According to this type of analysis, an item is generated in each of the component symbols 904 and/or in a file that is not a leaf node for the first file system. In element symbol 906, a leaf node can be determined to exist in the first file system, where a file backup item is established. The file backup project is a project related to a second file system that utilizes a type of composite entity to present a unit of information. At component symbol 908, the file backup item is supplemented and/or delivered with a file, a file stream, an attribute, a security, etc., to present the file as an item in the second file system. At component symbol 910, the file backup item is used to transfer the first file system to the second file system.

Figure 10 illustrates a method 1000 for facilitating the transfer of a file stream structure file system and a relay data related file system. In the component symbol 1002, a file stream structure file system (for example, the first file system) is analyzed. In component symbol 1004, a file backup item is generated, at least to some extent, based on an analysis of the first file system. The file backup project is a project related to a second file system, wherein a file and/or a file stream can supplement at least one of its characteristics. In 1006, the file backup item can be used to transfer the first file system and the second file system.

In component symbol 1008, "ghosting" can be provided to ensure that the attribute is complete and synchronized between the first file system and the second file system. For example, a project that has been backed up and restored can be generated to be a copy of another file backup project, but does not include a file stream. In addition, a backup restore can be provided, which is used to generate a backup restored project and/or convert an existing project into a backed up restore project. In addition, unghosting can be utilized, which is used to convert a backup and restore project into a normal project. In component symbol 1010, an attribute from the first file system can be combined and/or utilized with a file backup item associated with the second file system. The first file system may include an attribute that may be, but is not limited to, read only, compressed, recorded, etc., where a single element and/or a byte may represent such attributes. It should be understood that such attributes can be incorporated into the second file system by the file backup item.

At element symbol 1012, attribute tunneling can be utilized and/or a DAG. The attribute tunneling may provide a swap of a file stream between at least two file backup items to allow for retention of resources and/or change of name between temporary files in the second file system. The DAG provides an illustration of a link item without a loop. At component symbol 1014, the application interface from the first file system can be utilized with the second file system by using the file backup item, which provides complete integration. In other words, the file backup project not only contains the relay data attributes associated with one item and one item, but also the file stream related to the item. The file backup item can be operated by an application interface associated with the second file system and can be operated by the application interface portion of the first file system.

In order to provide a description of the various aspects of the invention, FIG. 11 and FIG. 12 and the following discussion will provide a brief, general description of a suitable computing environment in which several aspects of the invention may be implemented. While the present invention has been described above as a generalized content of computer executable commands for executing a computer program on a regional computer and/or remote computer, those skilled in the art will appreciate that the present invention can be combined with other programming modules. To implement. In general, program modules include routines, programs, components, data structures, and the like that perform special tasks and/or implement particular abstract data types.

Moreover, those skilled in the art will appreciate that the method of the present invention can be implemented in other computer system types, including single processor or multiprocessor computer systems, mini computers, host computers, personal computers, laptop devices, application microprocessors. And/or programmable consumer electronics and other similar products, each of which can effectively interface with one or more related devices. The illustrative aspects of the present invention can also be implemented in a distributed computing environment that performs certain tasks by remote processing devices coupled through a communications network. However, some (assuming not all) aspects of the invention may be implemented on a stand-alone computer. In a distributed computing environment, program modules may be located in local and/or remote memory storage devices.

Figure 11 is a pictorial block of a simple computing environment 1100 to which the present invention may be applied. The system 1100 includes one or more clients 1110. The client 1110 can be hardware and/or software (eg, related serials, programs, computing devices). The system 1100 also includes one or more servers 1120. The server 1120 can be hardware and/or software (eg, related serials, programs, computing devices). The server 1120, for example, may overlay related concatenations to perform the conversion by using the present invention.

A possible exchange between a client 1110 and a server 1120 can be transferred between two or more computer programs in a packet format. The system 1100 includes a communication structure 1140 that can be used to facilitate communication between the client 1110 and the server 1120. The client 1110 can be used to couple to one or more customer profile stores 1150 for storing information locally to the client 1110. Similarly, the server 1120 can be coupled to one or more server data stores 1130 for storing local information to the server 1120.

Referring to Fig. 12, an exemplary environment 1200 for implementing several aspects of the present invention includes a computer 1212. The computer 1212 includes a processing unit 1214, a system memory 1216, and a system bus 1218. The system bus 1218 is coupled to the system component, including but not limited to: a system component coupled to the system memory 1216 to the processing unit 1214. The processing unit can be of all available processors. Dual microprocessors and other multiprocessor architectures are also available as processor unit 1214.

The system bus 1218 can be comprised of the memory bus or memory controller, a peripheral bus or external bus, and/or a use of any kind of available bus structure (including, but not limited to, an industry standard architecture) (ISA), Micro Channel Architecture (MSA), Extended ISA (EISA), Smart Electronic Driver (IDE), VESA Area Bus (VLB), Peripheral Component Connection Interface (PCI), Card Bus, Universal Serial Bus (USB), Accelerated Graphics Interface (AGP), PC Memory Card International Association Bus (PCMCIA), High Speed Peripheral Data Transfer Interface (Firewire) (IEEE 1394) and Small Computer System Interface (SCSI) Any of several busbar structures in a local busbar.

The system memory 1216 includes a volatile memory 1220 and a non-volatile memory 1222. The basic program is included to transfer information between components within the computer 1212, for example, the basic output/input system (BIOS) during startup is stored in the non-volatile memory 1222. By way of illustration and not limitation, the non-volatile memory 1222 can include: read only memory (ROM), programmable read only memory (PROM), current programmable read only memory (EPROM), current can be Eliminate programmable read-only memory (EEPROM) or flash memory. Volatile memory 1220 includes random access memory (RAM), which acts as external cache memory. By way of illustration and without limitation, RAM can be of many types, such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), dual Data Rate Synchronous Dynamic Random Access Memory (DDR SDRAM), Direct Rambus Random Access Memory (RDRAM), Direct Rambus Dynamic Random Access Memory (DRDRAM), and Rambus Dynamic Random Access Memory (RDRAM) .

Computer 1212 also includes removable/non-removable, volatile/non-volatile computer storage media. Figure 12 illustrates, for example, a disc storage 1224. The disc storage 1224 includes devices, but is not limited to: a disk drive, a floppy disk drive, a tape drive, a Jaz disk drive, a Zip disk drive, an LS-100 disk drive, a flash memory card, or a memory stick. In addition, the disc storage 1224 may be included on its own or in combination with other storage media (including, but not limited to, an optical disc device such as a compact disc drive (CD-ROM), a CD-R drive, a rewritable optical disc. Storage media for a CD-RW drive or a variety of digital compact disc players (DVD-ROM). To facilitate coupling of the disk storage device 1224 to the system busbar 1218, a removable or non-removable interface is typically utilized, such as interface 1226.

It should be understood that the software described in FIG. 12 acts as a medium between the user and the basic computer resources in the appropriate operating environment 1200. Such software includes an operating system 1228. The operating system 1228 can be stored on the disc storage 1224 for controlling and distributing resources of the computer system 1212. The system application 1230 is stored in the system memory 1216 or the disk storage 1224 via the operating system 1228 via the program module 1232 and the program data 1234 to facilitate resource management. It will be appreciated that the invention can be used with a combination of several operating systems or operating systems.

A user enters a command or data via the input device 1236 to enter the computer 1212. The input device 1236 includes, but is not limited to: a pointing device, such as: a mouse, a trackball, a stylus, a touch pad, a keyboard, a microphone, a joystick, a game pad. ), satellite dish, scanner, TV tuner, digital camera, digital video camera, webcam, etc. These and other input devices are coupled to the processing unit 1214 via the interface bus 1218 via the interface 埠 1238. The interface 埠 1238 includes, for example, a series of cymbals, a flat cymbal, a game cymbal, and a 10,000 serial bus (USB). Output device 1240 uses some of the same types of input device 1236. Thus, for example, a USB port may be used to provide input to the computer 1212 and output information from the computer 1212 to an output device 1240. Output adapter 1242 provides instructions for certain output devices 1240 such as screens, loudspeakers, and printers, and in other output devices 1240, which require special adapters. The output adapter 1242 includes, by way of illustration and not limitation, providing an image and sound card having a connection path between the output device 1240 and the system bus 1218. It should be noted that systems of other devices and/or devices provide output and input capabilities, such as remote computer 1244.

The computer 1212 can be connected to one or more remote computers in a network environment using a logical connection, such as in a network environment of a remote computer 1244. The remote computer 1244 can be a personal computer, a server, a router, a network personal computer, a workstation, a microprocessor application device, a peer device or other general network node, etc., and generally includes many or All devices associated with computer 1212 are described. For the sake of simplicity, only one memory storage device 1246 is used to illustrate the remote computer 1244. The remote computer 1244 is logically coupled to the computer 1212 via a network interface 1248 and then physically coupled by the communication network 1250. The network interface 1248 includes wired and/or wireless communication networks, such as a local area network (LAN) and a wide area network (WAN). LAN technology includes: Fiber Distributed Data Interface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet, Token Ring, and more. WAN technologies include, but are not limited to, point-to-point chains, circuit-switched networks such as the Integrated Services Digital Network (ISDN) and its variants, packet switched networks, and Digital Subscriber Loop (DSL).

The communication network 1250 means a hardware/software for coupling the network interface 1248 to the bus 1218. When communication network 1250 is displayed to clearly illustrate the interior of computer 1212, it can also be external to computer 1212. The hardware/software required to couple the network interface 1248 is for explanation purposes only, internal and external technologies such as data machines including standard telephone grade data machines, cable modems and DSL modems, ISDN Adapter and Ethernet card.

The above examples of the present invention are included in the above description, and it is of course impossible to describe all of the methods and combinations of elements of the present invention. However, those skilled in the art will appreciate that the invention may be in various combinations and permutations. Accordingly, the present invention includes all modifications, variations and variations of the spirit and scope of the invention.

In particular, with respect to the various functions performed by the elements, devices, circuits, systems, etc. described above, unless otherwise indicated, the nouns (including the so-called "components") are used to describe that such elements are intended to correspond to An element that performs the function of a specific description of any element (eg, a functional equivalent) of a particular function of the element, even if it is not structurally equivalent to the structure shown herein, performs an exemplary aspect of the invention herein. Features. In this regard, it should be understood that the present invention comprises a system and a computer readable medium having computer executable instructions for performing the acts and/or events of the methods of the present invention.

Additionally, although one or more embodiments have been disclosed, a particular feature of the invention has been disclosed. Such features may be combined with other features of one or more other embodiments if needed and advantageous for any given or particular application. In addition, the terms "including "includes" and "including" and their variations mean that they have the same "include" as the noun "including "comprising".

102. . . File system

104. . . File system

106. . . File system adapter

108. . . interface

202. . . File system

204. . . File system

206. . . File system adapter

210. . . Analysis component

212. . . Generating component

302. . . File system

304. . . File system

306. . . File system adapter

310. . . Attribute component

312. . . Relay data processing component

402. . . File system

404. . . File system

406. . . File system adapter

410. . . Attribute tunneling component

412. . . Backup and restore component

504‧‧‧File System

506‧‧‧File System

502‧‧‧File backup project

508‧‧‧Semantic layer

510‧‧‧File Streaming

512‧‧‧Archive properties

514‧‧‧Activity status

516‧‧‧Change unit

518‧‧‧Project Information

602‧‧‧File System

604‧‧‧File System

606‧‧‧File System Adapter

608‧‧‧ directed non-cyclic graph components

702‧‧‧File System

704‧‧‧File System

706‧‧‧File System Adapter

708‧‧‧Smart components

710‧‧‧Display components

1110‧‧‧Client

1120‧‧‧Server

1130‧‧‧Server data storage

1140‧‧‧Communication structure

1150‧‧‧Client data storage

1212‧‧‧ computer

1214. . . Processing unit

1216. . . System memory

1220. . . Volatile memory

1222. . . Non-volatile memory

1224. . . Disk storage

1226. . . interface

1228. . . working system

1230. . . application

1232. . . Module

1234. . . data

1236. . . Input device

1238. . . Interface埠

1240. . . Output device

1242. . . Output adapter

1244. . . Remote computer

1246. . . Memory storage

1248. . . Network interface

1250. . . Communication network

Figure 1 is a block diagram of an example system that facilitates the transfer of a file stream related file system and a relay data related file system.

Figure 2 is a block diagram of an example system that facilitates the transfer of at least two different file systems to provide consistency.

Figure 3 is a block diagram of an example system that facilitates the transfer of a file stream related file system and a relay data related file system.

Figure 4 is a block diagram of an example system that facilitates synchronization of at least two different file systems.

Figure 5 is a block diagram of a file backup project that facilitates the transfer of a file system to a different file system.

Figure 6 is a block diagram of an exemplary system that facilitates the transfer of a file stream related file system and a relay data related file system.

Figure 7 is a block diagram of an example system that facilitates the transfer of a file stream related file system and a relay data related file system.

Figure 8 is an example method for transferring at least two different file systems to provide consistency.

Figure 9 is an example method for transferring a file system to a different file system.

Figure 10 is an exemplary method for transferring a file stream related file system and a relay data related file system.

Figure 11 is an example network environment in which aspects of the invention may be used.

Figure 12 is an example operating environment for practicing the present invention.

102‧‧‧File System

104‧‧‧File System

106‧‧‧File System Adapter

108‧‧‧ interface

Claims (18)

A system implemented on a computer readable storage medium for providing consistency between different file systems, the system comprising: an interface for receiving a first from a first file system Data of the file and receiving information about a second file from a second file system, wherein the first file system and the second file system are different file system types, and the second file system is the first a different representation of the file; and a file system adapter that provides consistency between the first file system and the second file system by using a file backup item, the file backup item Supplemented by the received data from the first file system and the second file system to provide at least one of a destination feature and a file stream, the file stream being related to the project, The first file and the second file are allowed to be controlled by at least one of an application interface of the first file system and an application interface of the second file system. The system of claim 1, wherein the first file system is at least one of a 16-bit file system and a 32-bit file system, the first file system utilizing a file and a directory and a Related file streams to provide more spatial structure for an application. The system of claim 1, wherein the second file system is a file storage system that defines a project, a subproject, a feature, and At least one of the relationships is used to represent information in a composite type. The system of claim 1, further comprising an analysis component that analyzes the first file system to determine a directory, a file, a file stream, an attribute, a node, a leaf node, and a security feature. At least one of them. The system of claim 1, further comprising a generating component, which generates at least one of: a file backup item for a leaf node of the first file system, and a file for the first file system A project of a non-leaf node in the directory. The system of claim 1, further comprising an attribute element for associating an attribute of the first file located in the first file system to the file backup item, wherein the attribute is for the second File system use. In the system of claim 6, the attribute is a one-bit element representing at least one of: a read-only, a compressed file, or an archived file. The system of claim 1, further comprising a relay data processor component that synchronizes at least one field between the file backup item and the first file located in the first file system. The system of claim 8, wherein the relay data processor provides at least one of: when modifying a feature in the first file in the first file system, the file is located in the file backup item And updating a new field in an appropriate field in the second file in the second file system; or when changing a feature in the second file of the second file system, the registration is in the file backup A new value is adjusted in an appropriate field in the first file in the project and in the first file system. The system of claim 1, further comprising a backup and restore component, the component providing at least one of the following: a backup restore operation, the backup restore operation generating a backup restore project, the backup restore project Copying one of the file backup items but not including a file stream; or an anti-backup restore operation, the reverse backup restore operation converts the backed up restore item to the file backup item. The system of claim 1, further comprising an attribute threading component that provides synchronization of at least one file backup item, the synchronization being provided by allowing for at least one file backup item File stream swap (swap). For example, in the system of claim 11, the file stream is located in a file stream table, wherein the item ID can be swapped. For example, in the system described in claim 1, the file backup item includes at least one of the following: a semantic layer, a file stream, an archive attribute, a physical item status, a change unit, or a project material. The system of claim 1, further comprising a directed loopless map (DAG) component, wherein the component provides a connection project map without a cycle. A computer deployment method for providing consistency between different file systems, comprising the steps of: analyzing a first file system, the analysis step for an application, utilizing a file and a directory with a related file stream Providing more structure in the space; generating a file backup project, the project being supplemented by the file to provide at least one of: one of the characteristics of the project, and one of the file streams associated with the project; The file backup item provides consistency of file access of the application between the first file system and a second file system, wherein the first file system and the second file system are file system types different from each other. The method of claim 15 further includes at least one of the following steps: Establishing a project for one non-leaf node in the first file system; generating the file backup item for one leaf node in the first file system; combining attributes from the file with the file backup item; and allowing for use by One of the first file system application interface and one of the application interfaces for the second file system are controlled by at least one of the application interfaces. The method of claim 15, further comprising at least one of the following steps: providing a backup restore and a reverse backup to restore at least one of the following; utilizing attributes to wear; and utilizing the connected items To the no-loop diagram, there is no loop for these connected projects. A system implemented on a computer readable storage medium for providing consistency between different file systems, the system comprising: a means for receiving data for use in a first file system Receiving information about a first file and a second file system receiving data about a second file, wherein the first file system and the second file system are different file system types, and the second file system a distinct representation of the first file; and a means for providing consistency by providing a consistent file between the first file system and the second file system by using a file backup item The file backup project is supplemented by the received data from the first file system and the second file system to provide at least one of a purpose-specific feature and a file stream, the file stream related In the project, the first file and the second file are controlled by at least one of an application interface of the first file system and an application interface of the second file system.