Automatic view selection

A data system user interface that can employ different data collection renderers (e.g., views) based on an attribute of the content of a view-set (e.g., list, folder, directory) is provided. In accordance with aspects of the subject invention, views that are suitable to present certain types of content can be automatically selected. This automatic selection can employ the use of more specialized, optimized views based on the content of the view-set. The contents of the view-set can be analyzed and matched against an extensible set of view selection rules. It will be understood that, although the custom view can have a completely different visual appearance from the standard, default and/or generic view, the subject invention enables custom views to run within the same window as the standard view.

TECHNICAL FIELD

This invention is related to computer systems and more particularly to a system and method to instantiate a custom view-set renderer in accordance with a specified criteria and/or rule(s).

BACKGROUND OF THE INVENTION

Computer users today manage an increasingly large set of items, including their own documents, web-based contents, database search results, etc. Current user interface mechanisms are not designed to deal well with such large working sets. Although some user interface systems today are capable of providing specialized views which partially alleviate this problem, the user is generally responsible for locating and applying these specialized views. Even in systems which may select a “default view”—such as a photo view, there is no facility for composing a multitude of specialized views.

Thus a need exists for a system that addresses both of these issues. First, a system that analyzes data prior to its display and dynamically selects the most helpful and appropriate view based on a variety of environmental parameters is needed. Secondly, an unmet need exists for a system that allows for arbitrary and recursive combinations of specialized views, providing a broad space of both user-guided and rule-guided composite specialized views. Such a mechanism (e.g., via management applications) can automatically provide a user with a clear and comprehensive depiction of the contents.

Recently, rule-based systems and applications have emerged to personalize and/or customize applications in an effort to streamline efficiencies related to computing techniques. However, rule-based systems have not been applied to collections of data and/or view-set management applications.

Conventionally, computer systems and applications employ a standard and/or default rendering technique (e.g., standard detail list view) to present contents of a data collection and/or file system to a user. This default list view merely provides a limited listing of programs and/or files. For example, in one implementation, an alphabetical list is provided which is categorized by application name without regard to a specific file type. By way of further example, a user could manually customize or sort the list in a number of ways including, by file type, alphabetically, size, date, etc.

In this regard, many computer programs and applications provide a mechanism to allow a user to deviate from the default view thereby manually selecting a more specialized method to display the contents of a file system or data store (e.g., view-set). In other words, traditional desktop operating system environments allow a user to manually select from different views each of which displays directory contents in a different way. By way of example, a user can choose an icon view to display a directory in a manner that presents icons depicting specific file types. This icon view presents a small or large icon of the file type as manually specified by the user. In another example, a thumbnail view could be manually selected and thereby employed to display a directory containing image files. This view renderer presents a thumbnail image of each image file in a directory (e.g., view-set). Such existing viewers have the limitation of being homogenous. For example, only one view-set-renderer can be applied to a given view-set. As well, there is not facility for composition of view-set-renderers to different sections of a given view-set.

In addition to the need to customize and/or personalize view selection schemes based upon user preference or application type, advances in technology and hardware support a need to further manipulate view schemes in accordance with hardware constraints. Technological advances in communication devices equipped with computing power (e.g., smart-phones, personal digital assistants (PDAs)) support the need to provide for a system and/or method to present data in relation to the specifications of hardware devices and/or displays. By way of example, the specifications of a PDA display greatly impact the limitations of a view-set renderer as compared to a desktop personal computer (PC) equipped with a 19-inch monitor.

Although conventional systems provide limited ability to manually select pre-defined renderers of view-sets, there is a substantial unmet need to provide a system and/or methodology that allows a user to customize and select presentation characteristics (e.g., view-set renderer) to dynamically and automatically display the contents of a data store (e.g., view-set). Because the invention provides a wide variety of specialized view-set renderers, there is a growing need for the system to automatically select view-set renderers based on the characteristics of the view-set and the display environment. Moreover, in addition to standard desktop PC's, there is an unmet need to apply this functionality to today's continually emerging portable communications devices.

SUMMARY OF THE INVENTION

Collections of data, such as file system directories or search results, (e.g., view-sets) can be presented in a uniform manner without regard for the attributes (e.g., size or type) of their contents. The subject invention disclosed and claimed herein, in one aspect thereof, comprises a data system user interface (UI) that can provide different data renderers (e.g., views) based on an attribute of the content of a view-set (e.g., list, folder, directory, search result). In accordance with aspects of the subject invention, views that are suitable to present certain types of content can be automatically selected. This automatic selection can employ the use of more specialized and optimized views based on the content of the view-set. The contents of the view-set can be analyzed and matched against an extensible set of view selection rules. It will be understood that, although the custom view can have a completely different visual appearance from the standard, default and/or generic view, the subject invention enables custom views to run within the same window as the standard view.

In one aspect of the invention, a system that facilitates presenting data is provided. The system can include an analyzer component that determines a characteristic of the content of a view-set component. It will be appreciated that the characteristic can be any view-set attribute. By way of example, the characteristic can include, but is not limited to, a file type, size, origination date, location, etc. It will further be understood that a file type can include any electronic file type known in the art including but, not limited to word processing, text, image, spreadsheet, audio documents or the like.

The system can further include a view selection component that automatically selects a renderer (e.g., view) as a function of the characteristic. The renderer can facilitate automatically presenting the content, or subset thereof, of the view-set component. It is contemplated that all or a portion of the content can be rendered (e.g., displayed) to a user via a display or other visual device.

In yet another aspect thereof, the content of a view-set can include a query result. For instance, a view-set can include the results of an Internet or any database search. In the case of an Internet search, it will be appreciated that the content of the view-set can include the results of the query in the form of hyperlinks or the like.

In still another aspect of the subject invention, a view selection component can employ a rule-based decision mechanism. In accordance thereto, a rule engine component that automatically selects a rule can be provided. Additionally, a rule evaluation component that applies the rule as a function of the characteristic to select a renderer can be provided. It will be appreciated that the rule engine component can be located remotely from the rule evaluation component or any other component of the system.

In another alternative aspect, an artificial intelligence (AI) component that predicts a user intention as a function of historical user criteria can be provided in place of, or in addition to, the rule-based decision components. The AI component can include an inference component that facilitates automatic selection of a renderer as a function of the user intention with respect to the characteristic. The inference component can employ a utility and/or statistical based analyses in performing the automatic selection. Furthermore, the view selection component can dynamically select the renderer as a function of a state of an application or other component.

In still another aspect, the system can be recursive in operation. For example, the content of the view-set component can include one or more sub-view-set components. The analyzer component can determine a sub-view-set characteristic in accordance with the sub-view-set component. In accordance thereto, the view selection component can dynamically and automatically select a sub-view-set rendering as a function of the sub-view-set characteristic to render at least a subset of the sub-view-set component.

DETAILED DESCRIPTION OF THE INVENTION

In accordance with the subject invention, the display of the contents (e.g., files, folders, query results) within in a view-set can be specialized based on any desired criteria (e.g., metadata, file type, size, date). By way of example, the presentation of information can be based upon the type and/or number of items being displayed. As will be appreciated, the systems and methodologies described herein can effect a display area to be used more efficiently. This invention can be particularly useful in light of the emerging handheld devices which employ smaller and more compact display systems. As well, the systems and methodologies disclosed herein can assist a user to more quickly and efficiently identify the contents of various directories and/or files by displaying the contents in a more comprehensive manner than conventional systems.

As discussed supra, contemporary desktop operating system environments allow a user to manually select from a limited number of predefined views, each of which displays directory contents in a different manner. In various aspects of the subject invention, specialized view-set renderers (e.g., view) can be selected dynamically and/or automatically based on any desired criteria (e.g., metadata, file type, size, age). In other words, view-set renderers that are suitable for certain types of files can be automatically selected thus allowing for the use of more specialized and optimized views based on the content that is to be presented.

Referring now toFIG. 1, there is illustrated a schematic representation of an aspect of a system100that facilitates data presentation in accordance with the subject invention. Generally, the system100can include a data store component102having view-set component(s)104therein. Further, the system100can include a view-set analyzer component106and a view selection component108.

The data store component102can include view-set components 1 to N, where N is an integer. View-set components 1 to N can be referred to collectively or individually as view-set components104as illustrated. View-set component104can be any compilation of and can include any number of electronic items, records or documents. By way of example, view-set component104can be a single document, list, folder, directory, query result or the like. Moreover, it is to be understood that view-set component104can include one or multiple electronic files or documents of diverse file types (e.g., spreadsheet, word processing, image, text, hyperlink). It will be appreciated that view-set component104can alternatively include a sub-view-set(s) therein.

One aspect of the subject invention is directed to a system and method whereby desktop operating system user interfaces (UIs) can facilitate the presentation of the contents by a renderer (e.g., view) of various view-sets104(e.g., directories, lists). As previously discussed, in conventional systems, view-sets104were usually presented in either a default or manually selected scheme without regard to application and/or user preference(s). In contrast and in accordance with various aspects, the subject system and/or methodology can dynamically and/or automatically invoke custom (e.g., user/application defined or predetermined) view-set renderers (e.g., views) with respect to specific data systems thereby presenting the contents in a user-friendly, comprehensive and efficient manner.

The system100can further include a view-set analyzer component106that can facilitate determination of a characteristic (e.g., metadata, file type, file size) from the view-set component104. The determined characteristic can be utilized by the system100in the selection of a custom view-set renderer (e.g., view). It will be appreciated that the functionality of the view-set analyzer component106can be integrated into other evaluation or decision-making components included within the view selection component108. These alternate aspects will be discussed in greater detail infra.

Finally, the view selection component108can be configured to select an appropriate view-set renderer or view (e.g., list, thumbnail, filmstrip) in accordance with the output (e.g., characteristic) of the view-set analyzer component106. In other words, based upon the boundary and contents of the view-set104, the view selection component108can automatically choose a renderer (e.g., view) to comprehensively present the view-set component104. As will be later discussed, the view selection component108can be configured to base a selection upon any desired criteria available. By way of example, the view selection component108can be configured to select a renderer (e.g., view) based upon a file type. For instance, suppose a view-set component104contains three word processing documents and five image files. The system can be pre-configured or programmed to automatically select a filmstrip view based upon a majority of the files being image files. Likewise, if three image files are subsequently removed leaving three word processing files and two image files, the system can dynamically present the contents using a tile view that illustrates a tile to identify the file type of each document. It is to be appreciated that this situation is exemplary and that any desired custom view and/or criteria can be employed in accordance with the present system.

Referring again to the exemplary aspect ofFIG. 1, once a set of particulars and/or characteristics of the contents of the view-set component104are determined (e.g., via view-set analyzer component106), the system100can be configured to employ the view selection component108to automatically select and instantiate an appropriate renderer based upon the specific file types contained within the view-set component104. In the exemplary situation, the view selection component108can be configured to implement a combination thumbnail view of the image files together with an icon view of the word processing documents. Alternatively, the view selection component108can be automatically configured to invoke a filmstrip view as a result of a majority of the files in the subject view-set component104being image files. Although specific examples and aspects are discussed herein, it is to be understood that any number of optional views and/or decision schemes can be employed and are to be considered within the scope and functionality of the claimed invention.

In alternative aspects and by way of further example, the view selection component108can be configured with a decision-making mechanism in the form of a rule engine whereby a rule can be applied to the view-set component104thus automatically selecting an appropriate view component. In an alternate aspect, an artificial intelligence component can be employed individually or in combination with other evaluation schemes in order to effect view selection based upon contents of a view-set. These alternative aspects will be discussed in greater detail infra.

Further, it is to be understood that the systems and methodologies described herein can be effected in a recursive manner. In other words, the view-sets104can be dynamically and/or automatically customized at any level within the data store component102or view-set104. Accordingly, sub-lists or sub-view-sets can be contained within parent lists whereby the components (e.g.,106,108) described supra can facilitate automatic view selection of a customized view at the subordinate level. By way of example, the view selection component108can look at the boundary of the view-set component104and select an appropriate renderer (e.g., view). In the event the selected renderer determines that the view-set contains an additional or sub-view-set (e.g., list, folder, query), the view selection component108can be re-invoked whereby an appropriate renderer can be selected to present the additional view-set. It is contemplated that the rendering functionality of the subject invention can be applied to present (e.g., render) a view-set or contents of a view-set to a user or other entity (e.g., application, component, module).

In another alternate aspect, the view selection component108can be configured to dynamically select a renderer (e.g., view) with respect to a type and/or state of an application. By way of example, suppose a user is employing a word processing application. The subject invention can be configured to facilitate selection of a custom view based upon the application or state within the application. In other words, if a user selects to insert or open a file within the application, the system can dynamically select a filmstrip or document view to assist in the insert/open operation in accordance to an image or text file respectively. This automated determination can select an appropriate view based upon a file type to comprehensively and efficiently aid the user in selecting the appropriate file(s) to open or insert.

It will be appreciated that automatically selecting the appropriate view can reduce the burden on a user to decide which view will be most efficient in light of the view-set contents. As well, dynamic selection can reduce the amount of user interface thereby eliminating potential error conditions or sub-optimal user experience and/or performance which can result from incorrect view selection.

Referring toFIG. 2and proceeding to202, a view-set (e.g., list, folder, query) is selected. In accordance with the subject invention, it is to be appreciated that a view-set can be manually or automatically selected. By way of example, the view-set can be manually selected by a user or automatically selected via an application or other system component. At204, the view-set is analyzed to determine its contents and characteristics thereof. As discussed supra, the functionality of analyzing the view-set can reside in a separate component as illustrated inFIG. 1or can alternatively be combined within the functionality of another component (e.g., view selection component). In either case, at204, a determination is made of the contents including other characteristics of the view-set.

Once analyzed, an implementation scheme (e.g., rule) can be applied at206to identify an appropriate renderer (e.g., view) in accordance with the contents and/or characteristic(s) of the view-set. It will be appreciated that the rule-based implementation to automatically and/or dynamically select a view can employ a predefined and/or programmed rule(s) based upon any desired criteria (e.g., file type, file size, hardware characteristics). By way of example, a user can establish a rule that selects a preferred view in accordance with a variety of predetermined circumstances.

In an exemplary aspect, a rule can be constructed to implement a filmstrip or thumbnail view when the contents of a view-set are, or a majority of the contents are, image files. In another aspect, a rule can be constructed to employ a historical detail or list view in the event that the creation date of the newest to the oldest document exceed a predefined threshold. In accordance with the disclosed aspects, it is to be appreciated that a “list” (e.g., view-set) can reside within a database component. As such, it is contemplated that the invention can facilitate access to additional information (e.g., rich metadata) whereby this additional information can be employed to assist in the dynamic determination and/or refinement of an appropriate renderer. For instance, suppose a user desires to display music files. The system can automatically determine an appropriate view (e.g., thumbnail of album cover). Further, because the system can reside in a database environment, it will be appreciated that the system can automatically refine and/or obtain additional information as a result of a chosen view. In the exemplary scenario, the system can further refine by obtaining an image of the artist or additional tracks consistent with an subject artist. In any case, it is to be appreciated that the system is capable of refining a view via a query.

Once identified, the system can instantiate the custom renderer at208to present the contents of the view-set. In accordance with the subject invention, it is to be appreciated that the presentation of the contents of a view-set discussed herein can be accomplished in any desired manner. By way of example, the contents can be presented directly to a user via a display or monitor. As well, the contents can be rendered to an application whereby, in accordance with other factors (e.g., handheld display size), the rendered presentation can be modified (e.g., scaled) to conform to predetermined specifications. Thus, the scaled view can then be displayed to a user via a handheld display device.

Continuing with the example and with reference toFIG. 3, a more detailed schematic view of a view selection component108is shown. As illustrated, view selection component108can generally include a rule engine component302, a rule evaluation component304and a custom view store component306. Custom view store component306can include views 1 to M, where M is an integer. It is to be appreciated that views 1 to M can be referred to individually or collectively as view308. Additionally, it is to be appreciated that views308can be retained in any technique known in the art. By way of example, views308can be retained utilizing any memory device including, but not limited to, buffered, cached, stored on a hard disk device or the like. As will be discussed infra, an optional artificial intelligence component (not shown) can be used together with, or in place of, the rule engine component302to automatically infer a rule.

In the exemplary aspect ofFIG. 3, the rule engine component302can be programmed or configured in accordance with a user-defined preference. As well, a rule can be established in accordance with a specific hardware configuration, in accordance with a software application, existing parent view (if being invoked recursively on a subview) or in accordance with any other environmental parameter, such as the current user. For example, a rule can be constructed in accordance with specific memory capacity and/or display mechanism of a device. In other words, as previously discussed, a rule can be established to take into consideration the specific limitations of a hardware device (e.g., display mechanism).

The rule evaluation component304facilitates application of the rule in accordance with the contents and characteristics determined by the view-set analyzer component106. Based upon the output of the rule evaluation component304, the view selection component108can select and invoke a custom view308from the custom view store component306. It is to be appreciated that the custom view component308can be any desired view or arrangement which is known or becomes known in the art. By way of example, the custom view component308can facilitate presentation in any manner including, but not limited to, list, detail, filmstrip, fish-eye, slideshow, icon, web layout, hierarchical, chronological or the like.

For ease of understanding,FIG. 4, illustrates a flow chart of an exemplary methodology in accordance with an alternate aspect of the subject invention. Referring toFIG. 4and proceeding to402, a directory (e.g., view-set) is selected. As previously discussed, the selection of a particular view-set or directory can be manually initiated by a user. Although the exemplary aspect is directed toward a system whereby a user manually initiates the selection, it is to be appreciated that any method of selecting a particular view-set can be employed in accordance with the claimed invention. By way further example, a directory and/or view-set can be dynamically and/or automatically selected via a computer program or application. For instance, the view-set can be dynamically selected by a query component as a result of an Internet search or query.

At404, the contents (e.g., files, hyperlinks, uniform resource locators (URLs)) of the view-set or directory are analyzed and matched against an extensible set of view selection rules. As previously discussed, this analyzing procedure can be performed by a view-set analyzer component106illustrated inFIG. 1. It will be appreciated that any suitable source code can employed to contrast a rule(s). By way of example, in an exemplary implementation, rules can be implemented in the form of any suitable computer language including, but not limited to T-SQL, C# source code or the like.

Based upon the contents of the view-set, or other desired attribute, at406, the system determines if an applicable rule exists. If at406no rule is found to be applicable to the contents of the directory, a generic or standard renderer (e.g., view) can be selected and instantiated at408. If, on the other hand, an applicable rule is found at406, a custom renderer (e.g., view) can be selected at410in accordance with the applicable rule. If more than one applicable rule is found, the rules can be ranked according to the specificity of the rule and the highest ranking (most specific) rule can be selected. Next, the custom renderer or view can be instantiated at412.

In either case, whether a custom or standard view is instantiated at412or408respectively, the system next determines if the recursive functionality of the invention is applicable at414. The recursive functionality is applicable if there are natural subgroupings of the data (such as a sub-directory if viewing a file system) or if the current custom viewer specifically expresses recursion. For example, in the case of a collection of photographs, documents, and videos, the most applicable rule could select a “media library view” the media library view could in turn group the view-set according to type (photograph, etc.) and then recurse on these sets. The result would be a “media library view” which contained, as subviews, a “photograph view”, a “video view” and a “document view”. It will be appreciated that there are many situations in which such recursive view construction is applicable. Once such applicability is determined, the system determines at416whether it is permitted. A user, for example, may indicate that sub-directories are not to be expanded. If present and requested, the system returns to402to select the directory and appropriate renderer. If a sub-directory is not present and/or not requested, the system methodology ends as illustrated. Those skilled in the art will understand that because the implementation disclosed herein supports hierarchical and/or nested views, the methodologies described can be repeated recursively as discussed supra.

It is to be appreciated that although the custom view can employ a completely different visual appearance from the standard view, it can run inside the same window as the standard or generic view(s) and vice versa. Additionally, the system can adapt the custom view to conform to specific hardware or desired criteria. By way of example, the system can be configured to dynamically select a photographic filmstrip view thereby adapting the view to conform to a target device. It will be appreciated that because pictures can be primarily identified by their visual contents rather than their title or other ancillary data, the filmstrip view can pack or align pictures closer together thereby suppressing the display of their title(s). Although this alignment can allow a greater density of presentation for images or photographs, this view may not be suitable for a display mechanism of a portable device. An exemplary rule can activate this filmstrip view when all, or a majority, of the contents of a directory are image files and the target device is capable of displaying such a rendered presentation. In the alternative, the rule can be configured to dynamically select and present the view-set via a substitute view which conforms with limited specifications of an alternate target device (e.g., PDA).

FIG. 5illustrates an exemplary UI, renderer or view according to an alternate aspect of the subject invention. It is to be appreciated however, that the subject invention is not limited to the examples shown and described herein. Referring toFIG. 5, a query results page is illustrated. In accordance with an aspect of the subject invention, an exemplary query results display500is illustrated as a composite view. This type of view can be employed to effect presentation emphasis with regard to more detailed information with respect to a given search result. In this aspect, iconized views have been instantiated for each of the sub-groupings of data. For the “Picture,” sub-group, however, a specialized “page” view (502) which shows all its members inline has been instantiated. Within that view, even more specific “photo” views (503) have been instantiated, which do not show the names of their items or any other details. In an alternate aspect, the results can be displayed utilizing a thumbnail image of the web page result.

A schematic diagram of another aspect of the subject invention is illustrated inFIG. 6. Generally,FIG. 6illustrates a system600including a view-set component104, view-set analyzer component106and a view selection component602. In particular, the view-set component104and the view-set analyzer component106have similar functionality as those discussed previously with reference toFIG. 1. On the other hand, the view selection component602of this aspect includes an artificial intelligence (AI) engine component604, an AI evaluation component606and the custom view store component306having view component(s)308therein.

In accordance with this aspect, the optional AI engine and evaluation components604,606can facilitate automatically performing various aspects (e.g., custom view selection, zoom in/out, scaling, arrangement) of the subject invention as described herein. The AI components604,606can optionally include an inference component that can further enhance automated aspects of the AI component utilizing, in part, inference based schemes to facilitate inferring intended actions to be performed at a given time and state. The AI-based aspects of the invention can be effected via any suitable machine-learning based technique and/or statistical-based techniques and/or probabilistic-based techniques.

In this alternate aspect as illustrated byFIG. 6, the subject invention (e.g., in connection with selecting a custom renderer) can optionally employ various AI based schemes for automatically carrying out various aspects thereof. Specifically, an AI engine604and evaluation components606can optionally be provided to implement aspects of the subject invention based upon AI processes (e.g., confidence, inference). For example, a process for determining an appropriate renderer (e.g., custom view component308) based upon contents of a view-set104can be facilitated via an automatic classifier system and process. Further, the optional AI engine604and evaluation components606can be employed to facilitate an automated process of configuration (e.g., scaling, zoom in/out) in accordance with hardware specifications.

A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, xn), to a confidence that the input belongs to a class, that is, f(x)=confidence(class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to prognose or infer an action that a user desires to be automatically performed. In the case of renderer selection, for example, attributes can be file types or other data-specific attributes derived from the file types and/or contents of a view-set, and the classes can be categories or other areas of interest.

As will be readily appreciated from the subject specification, the subject invention can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing user behavior, receiving extrinsic information). For example, SVM's can be configured via a learning or training phase within a classifier constructor and feature selection module. In other words, the use of expert systems, fuzzy logic, support vector machines, greedy search algorithms, rule-based systems, Bayesian models (e.g., Bayesian networks), neural networks, other non-linear training techniques, data fusion, utility-based analytical systems, systems employing Bayesian models, etc., are contemplated and are intended to fall within the scope of the hereto appended claims.

With reference again toFIG. 7, there is illustrated an exemplary environment700for implementing various aspects of the invention that includes a computer702, the computer702including a processing unit704, a system memory706and a system bus708. The system bus708couples system components including, but not limited to, the system memory706to the processing unit704. The processing unit704can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures may also be employed as the processing unit704.

The system bus708can be any of several types of bus structure that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory706includes read only memory (ROM)710and random access memory (RAM)712. A basic input/output system (BIOS) is stored in a non-volatile memory710such as ROM, EPROM, EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer702, such as during start-up. The RAM712can also include a high-speed RAM such as static RAM for caching data.

The computer702further includes an internal hard disk drive (HDD)714(e.g., EIDE, SATA), which internal hard disk drive714may also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD)716, (e.g., to read from or write to a removable diskette718) and an optical disk drive720, (e.g., reading a CD-ROM disk722or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive714, magnetic disk drive716and optical disk drive720can be connected to the system bus708by a hard disk drive interface724, a magnetic disk drive interface726and an optical drive interface728, respectively. The interface724for external drive implementations includes at least one or both of Universal Serial Bus (USB) and IEEE 1394 interface technologies.

A number of program modules can be stored in the drives and RAM712, including an operating system730, one or more application programs732, other program modules734and program data736. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM712. It is appreciated that the subject invention can be implemented with various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer702through one or more wired/wireless input devices, e.g., a keyboard738and a pointing device, such as a mouse740. Other input devices (not shown) may include a microphone, an IR remote control, a joystick, a game pad, a stylus pen, touch screen, or the like. These and other input devices are often connected to the processing unit704through an input device interface742that is coupled to the system bus708, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, etc.

A monitor744or other type of display device is also connected to the system bus708via an interface, such as a video adapter746. In addition to the monitor744, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

When used in a LAN networking environment, the computer702is connected to the local network752through a wired and/or wireless communication network interface or adapter756. The adaptor756may facilitate wired or wireless communication to the LAN752, which may also include a wireless access point disposed thereon for communicating with the wireless adaptor756. When used in a WAN networking environment, the computer702can include a modem758, or is connected to a communications server on the WAN754, or has other means for establishing communications over the WAN754, such as by way of the Internet. The modem758, which can be internal or external and a wired or wireless device, is connected to the system bus708via the serial port interface742. In a networked environment, program modules depicted relative to the computer702, or portions thereof, can be stored in the remote memory/storage device750. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

Referring now toFIG. 8, there is illustrated a schematic block diagram of an exemplary computing environment800in accordance with the subject invention. The system800includes one or more client(s)802. The client(s)802can be hardware and/or software (e.g., threads, processes, computing devices). The client(s)802can house cookie(s) and/or associated contextual information by employing the subject invention, for example. The system800also includes one or more server(s)804. The server(s)804can also be hardware and/or software (e.g., threads, processes, computing devices). The servers804can house threads to perform transformations by employing the subject invention, for example. One possible communication between a client802and a server804can be in the form of a data packet adapted to be transmitted between two or more computer processes. The data packet may include a cookie and/or associated contextual information, for example. The system800includes a communication framework806(e.g., a global communication network such as the Internet) that can be employed to facilitate communications between the client(s)802and the server(s)804.

Communications can be facilitated via a wired (including optical fiber) and/or wireless technology. The client(s)802are operatively connected to one or more client data store(s)808that can be employed to store information local to the client(s)802(e.g., cookie(s) and/or associated contextual information). Similarly, the server(s)804are operatively connected to one or more server data store(s)810that can be employed to store information local to the servers804.