Patent Publication Number: US-2012047384-A1

Title: Methods, systems, and computer program products for selecting a resource in response to a change in available energy

Description:
RELATED APPLICATIONS 
     This application is related to the following commonly owned U.S. patent applications, the entire disclosure of each being incorporated by reference herein: application Ser. No. ______, (Docket No 0125) filed on Aug. 17, 2010, entitled “Methods, Systems, and Program Products for Presenting an Indication of a Cost of Processing a Resource”; 
     application Ser. No. ______, (Docket No 0162) filed on Aug. 17, 2010, entitled “Methods, Systems, and Program Products for Selecting a Resource Based on a Measure of a Processing Cost”; and 
     application Ser. No.______, (Docket No 0123) filed on Aug. 17, 2010, entitled “Methods, Systems, and Program Products for Maintaining a Resource Based on a Cost of Energy”. 
    
    
     BACKGROUND 
     Many personalization options provided by computing devices consume energy not required to perform computing tasks. For example, a primary purpose of a desktop background is esthetic. Mouse pointer effects, window effects, document previews, and many other examples exist. Currently, a user can configure a device to automatically turn such features on or off based on whether the device is plugged into an electrical outlet or drawing energy from a battery. Other features, such as the brightness of a display, can be adjusted based on whether a device is plugged in or not. These configuration options give no consideration to the resources being processed by the corresponding features. 
     Accordingly, there exists a need for methods, systems, and computer program products for selecting a resource in response to a change in available energy. 
     SUMMARY 
     The following presents a simplified summary of the disclosure in order to provide a basic understanding to the reader. This summary is not an extensive overview of the disclosure and it does not identify key/critical elements of the invention or delineate the scope of the invention. Its sole purpose is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later. 
     Methods and systems are described for selecting a resource in response to a change in available energy. In one aspect, the method includes detecting a change in a first energy source during processing of a first resource by a program component. The method further includes selecting a second resource based on a second measure of an energy cost for processing the second resource. The method still further includes identifying the second resource to the program component for processing in response to detecting the change. 
     Further, a system for selecting a resource in response to a change in available energy is described. The system includes a energy monitor component, a cost monitor component, and a resource director component adapted for operation in an execution environment. The system includes the energy monitor component configured for detecting a change in a first energy source during processing of a first resource by a program component. The system further includes the cost monitor component configured for selecting a second resource based on a second measure of an energy cost for processing the second resource. The system still further includes the resource director component configured for identifying the second resource to the program component for processing in response to detecting the change. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Objects and advantages of the present invention will become apparent to those skilled in the art upon reading this description in conjunction with the accompanying drawings, in which like reference numerals have been used to designate like or analogous elements, and in which: 
         FIG. 1  is a block diagram illustrating an exemplary hardware device included in and/or otherwise providing an execution environment in which the subject matter may be implemented; 
         FIG. 2  is a flow diagram illustrating a method for selecting a resource in response to a change in available energy according to an aspect of the subject matter described herein; 
         FIG. 3  is a block diagram illustrating an arrangement of components for selecting a resource in response to a change in available energy according to another aspect of the subject matter described herein; 
         FIG. 4   a  is a block diagram illustrating an arrangement of components for selecting a resource in response to a change in available energy according to another aspect of the subject matter described herein; 
         FIG. 4   b  is a block diagram illustrating an arrangement of components for selecting a resource in response to a change in available energy according to another aspect of the subject matter described herein; 
         FIG. 4   c  is a block diagram illustrating an arrangement of components for selecting a resource in response to a change in available energy according to another aspect of the subject matter described herein; 
         FIG. 4   d  is a block diagram illustrating an arrangement of components for selecting a resource in response to a change in available energy according to another aspect of the subject matter described herein; 
         FIG. 5  is a network diagram illustrating an exemplary system for selecting a resource in response to a change in available energy according to another aspect of the subject matter described herein; and 
         FIG. 6  is a diagram illustrating a user interface presented via a display according to another aspect of the subject matter described herein. 
     
    
    
     DETAILED DESCRIPTION 
     One or more aspects of the disclosure are described with reference to the drawings, wherein like reference numerals are generally utilized to refer to like elements throughout, and wherein the various structures are not necessarily drawn to scale. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects of the disclosure. It may be evident, however, to one skilled in the art, that one or more aspects of the disclosure may be practiced with a lesser degree of these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing one or more aspects of the disclosure. 
     An exemplary device included in an execution environment that may be configured according to the subject matter is illustrated in  FIG. 1 . An execution environment includes an arrangement of hardware and, optionally, software that may be further configured to include an arrangement of components for performing a method of the subject matter described herein. An execution environment includes and/or is otherwise provided by one or more devices. An execution environment may include a virtual execution environment including software components operating in a host execution environment. Exemplary devices included in or otherwise providing suitable execution environments for configuring according to the subject matter include personal computers, notebook computers, tablet computers, servers, handheld and other mobile devices, multiprocessor devices, distributed devices, consumer electronic devices, routers, communication servers, and/or other network-enabled devices. Those skilled in the art will understand that the components illustrated in  FIG. 1  are exemplary and may vary by particular execution environment. 
       FIG. 1  illustrates hardware device  100  included in execution environment  102 .  FIG. 1  illustrates that execution environment  102  includes instruction-processing unit (IPU)  104 , such as one or more microprocessors; physical IPU memory  106  including storage locations identified by addresses in a physical memory address space of IPU  104 ; persistent secondary storage  108 , such as one or more hard drives and/or flash storage media; input device adapter  110 , such as a key or keypad hardware, a keyboard adapter, and/or a mouse adapter; output device adapter  112 , such as a display and/or an audio adapter for presenting information to a user; a network interface component, illustrated by network interface adapter  114 , for communicating via a network such as a LAN and/or WAN; and a communication mechanism that couples elements  104 - 114 , illustrated as bus  116 . Elements  104 - 114  may be operatively coupled by various means. Bus  116  may comprise any type of bus architecture, including a memory bus, a peripheral bus, a local bus, and/or a switching fabric. 
     IPU  104  is an instruction execution machine, apparatus, or device. Exemplary IPUs include one or more microprocessors, digital signal processors (DSPs), graphics processing units, application-specific integrated circuits (ASICs), and/or field programmable gate arrays (FPGAs). In the description of the subject matter herein, the terms “IPU” and “processor” are used interchangeably. IPU  104  may access machine code instructions and data via one or more memory address spaces in addition to the physical memory address space. A memory address space includes addresses identifying locations in a processor memory. The addresses in a memory address space are included in defining a processor memory. IPU  104  may have more than one processor memory. Thus, IPU  104  may have more than one memory address space. IPU  104  may access a location in a processor memory by processing an address identifying the location. The processed address may be in an operand of a machine code instruction and/or may be identified in a register or other portion of IPU  104 . 
       FIG. 1  illustrates virtual IPU memory  118  spanning at least part of physical IPU memory  106  and at least part of persistent secondary storage  108 . Virtual memory addresses in a memory address space may be mapped to physical memory addresses identifying locations in physical IPU memory  106 . An address space for identifying locations in a virtual processor memory is referred to as a virtual memory address space; its addresses are referred to as virtual memory addresses; and its IPU memory is referred to as a virtual IPU memory or virtual memory. The terms “IPU memory” and “processor memory” are used interchangeably herein. Processor memory may refer to physical processor memory, such as IPU memory  106 , and/or may refer to virtual processor memory, such as virtual IPU memory  118 , depending on the context in which the term is used. 
     Physical IPU memory  106  may include various types of memory technologies. Exemplary memory technologies include static random access memory (SRAM) and/or dynamic RAM (DRAM) including variants such as dual data rate synchronous DRAM (DDR SDRAM), error correcting code synchronous DRAM (ECC SDRAM), and/or RAMBUS DRAM (RDRAM). Physical IPU memory  106  may include volatile memory as illustrated in the previous sentence and/or may include nonvolatile memory such as nonvolatile flash RAM (NVRAM) and/or ROM. 
     Persistent secondary storage  108  may include one or more flash memory storage devices, one or more hard disk drives, one or more magnetic disk drives, and/or one or more optical disk drives. Persistent secondary storage may include removable media. The drives and their associated computer readable storage media provide volatile and/or nonvolatile storage for computer readable instructions, data structures, program components, and other data for execution environment  102 . 
     Execution environment  102  may include software components stored in persistent secondary storage  108 , in remote storage accessible via a network, and/or in a processor memory.  FIG. 1  illustrates execution environment  102  including operating system  120 , one or more applications  122 , and other program code and/or data components illustrated by other libraries and subsystems  124 . In an aspect, some or all software components may be stored in locations accessible to IPU  104  in a shared memory address space shared by the software components. The software components accessed via the shared memory address space are stored in a shared processor memory defined by the shared memory address space. In another aspect, a first software component may be stored in one or more locations accessed by IPU  104  in a first address space and a second software component may be stored in one or more locations accessed by IPU  104  in a second address space. The first software component is stored in a first processor memory defined by the first address space and the second software component is stored in a second processor memory defined by the second address space. 
     Software components typically include instructions executed by IPU  104  in a computing context referred to as a “process”. A process may include one or more “threads”. A “thread” includes a sequence of instructions executed by IPU  104  in a computing sub-context of a process. The terms “thread” and “process” may be used interchangeably herein when a process includes only one thread. 
     Execution environment  102  may receive user-provided information via one or more input devices illustrated by input device  128 . Input device  128  provides input information to other components in execution environment  102  via input device adapter  110 . Execution environment  102  may include an input device adapter for a keyboard, a touch screen, a microphone, a joystick, a television receiver, a video camera, a still camera, a document scanner, a fax, a phone, a modem, a network interface adapter, and/or a pointing device, to name a few exemplary input devices. 
     Input device  128  included in execution environment  102  may be included in device  100  as  FIG. 1  illustrates or may be external (not shown) to device  100 . Execution environment  102  may include one or more internal and/or external input devices. External input devices may be connected to device  100  via corresponding communication interfaces such as a serial port, a parallel port, and/or a universal serial bus (USB) port. Input device adapter  110  receives input and provides a representation to bus  116  to be received by IPU  104 , physical IPU memory  106 , and/or other components included in execution environment  102 . 
     Output device  130  in  FIG. 1  exemplifies one or more output devices that may be included in and/or may be external to and operatively coupled to device  100 . For example, output device  130  is illustrated connected to bus  116  via output device adapter  112 . Output device  130  may be a display device. Exemplary display devices include liquid crystal displays (LCDs), light emitting diode (LED) displays, and projectors. Output device  130  presents output of execution environment  102  to one or more users. In some embodiments, an input device may also include an output device. Examples include a phone, a joystick, and/or a touch screen. In addition to various types of display devices, exemplary output devices include printers, speakers, tactile output devices such as motion producing devices, and other output devices producing sensory information detectable by a user. 
     A device included in or otherwise providing an execution environment may operate in a networked environment communicating with one or more devices via one or more network interface components. The terms “communication interface component” and “network interface component” are used interchangeably.  FIG. 1  illustrates network interface adapter (NIA)  114  as a network interface component included in execution environment  102  to operatively couple device  100  to a network. A network interface component includes a network interface hardware (NIH) component and optionally a software component. 
     Exemplary network interface components include network interface controller components, network interface cards, network interface adapters, and line cards. A node may include one or more network interface components to interoperate with a wired network and/or a wireless network. Exemplary wireless networks include a BLUETOOTH network, a wireless 802.11 network, and/or a wireless telephony network (e.g., a cellular, PCS, CDMA, and/or GSM network). Exemplary network interface components for wired networks include Ethernet adapters, Token-ring adapters, FDDI adapters, asynchronous transfer mode (ATM) adapters, and modems of various types. Exemplary wired and/or wireless networks include various types of LANs, WANs, and/or personal area networks (PANs). Exemplary networks also include intranets and internets such as the Internet. 
     The terms “network node” and “node” in this document both refer to a device having a network interface component for operatively coupling the device to a network. Further, the terms “device” and “node” used herein refer to one or more devices and nodes, respectively, providing and/or otherwise included in an execution environment unless clearly indicated otherwise. 
     The components of a user interface are generically referred to herein as “user interface elements”. More specifically, visual components of a user interface are referred to herein as “visual interface elements”. A visual interface element may be a visual component of a graphical user interface (GUI). Exemplary visual interface elements include windows, textboxes, sliders, list boxes, drop-down lists, spinners, various types of menus, toolbars, ribbons, combo boxes, tree views, grid views, navigation tabs, scrollbars, labels, tooltips, text in various fonts, balloons, dialog boxes, and various types of button controls including check boxes and radio buttons. An application interface may include one or more of the elements listed. Those skilled in the art will understand that this list is not exhaustive. The terms “visual representation”, “visual component”, and “visual interface element” are used interchangeably in this document. Other types of user interface elements include audio output components referred to as “audio interface elements”, tactile output components referred to as “tactile interface elements”, and the like. 
     A “user interface (UI) element handler” component, as the term is used in this document, includes a component configured to send information representing a program entity for presenting a user detectable representation of the program entity by an output device, such as a display. A “program entity” is an object included in and/or otherwise processed by an application or executable. The user detectable representation is presented based on the sent information. The sent information is referred to herein as “presentation information”. Presentation information may include data in one or more formats. Exemplary formats include image formats such as JPEG, video formats such as MP4, markup language data such as HTML and other XML-based markup, and/or instructions such as those defined by various script languages, byte code, and/or machine code. For example, a web page received by a browser from a remote application provider may include HTML ECMAScript, and/or byte code for presenting one or more user interface elements included in a user interface of the remote application. Components configured to send information representing one or more program entities for presenting particular types of output by particular types of output devices include visual interface elements, audio interface element handler components, tactile interface element handler components, and the like. 
     A representation of a program entity may be stored and/or otherwise maintained in a presentation space. As used in this document, the term “presentation space” refers to a storage region allocated and/or otherwise provided for storing presentation information, which may include audio, visual, tactile, and/or other sensory data for presentation by and/or on an output device. For example, a buffer for storing an image and/or text string may be a presentation space. A presentation space may be physically and/or logically contiguous or non-contiguous. A presentation space may have a virtual as well as a physical representation. A presentation space may include a storage location in processor memory, secondary storage, a memory of an output adapter device, and/or a storage medium of an output device. A screen of a display, for example, is a presentation space. 
     As used herein, the term “program” or “executable” refers to any data representation that may be translated into a set of machine code instructions and optionally associated program data. Thus, a program or executable may include an application, a shared or non-shared library, and a system command. Program representations other than machine code include object code, byte code, and source code. Object code includes a set of instructions and/or data elements that either are prepared for linking prior to loading or are loaded into an execution environment. When in an execution environment, object code may include references resolved by a linker and/or may include one or more unresolved references. The context in which this term is used will make clear that state of the object code when it is relevant. This definition can include machine code and virtual machine code, such as Java™ byte code. 
     As used herein, an “addressable entity” is a portion of a program, specifiable in programming language in source code. An addressable entity is addressable in a program component translated for a compatible execution environment from the source code. Examples of addressable entities include variables, constants, functions, subroutines, procedures, modules, methods, classes, objects, code blocks, and labeled instructions. A code block includes one or more instructions in a given scope specified in a programming language. An addressable entity may include a value. In some places in this document “addressable entity” refers to a value of an addressable entity. In these cases, the context will clearly indicate that the value is being referenced. 
     Addressable entities may be written in and/or translated to a number of different programming languages and/or representation languages, respectively. An addressable entity may be specified in and/or translated into source code, object code, machine code, byte code, and/or any intermediate languages for processing by an interpreter, compiler, linker, loader, or analogous tool. 
     The block diagram in  FIG. 3  illustrates an exemplary system for selecting a resource in response to a change in available energy according to the method illustrated in  FIG. 2 .  FIG. 3  illustrates a system, adapted for operation in an execution environment, such as execution environment  102  in  FIG. 1 , for performing the method illustrated in  FIG. 2 . The system illustrated includes a energy monitor component  302 , a cost monitor component  304 , and a resource director component  306 . The execution environment includes an instruction-processing unit, such as IPU  104 , for processing an instruction in at least one of the energy monitor component  302 , the cost monitor component  304 , and the resource director component  306 . Some or all of the exemplary components illustrated in  FIG. 3  may be adapted for performing the method illustrated in  FIG. 2  in a number of execution environments.  FIGS. 4   a - d  include block diagrams illustrating the components of  FIG. 3  and/or analogs of the components of  FIG. 3  adapted for operation in various execution environments  401  including or otherwise provided by one or more nodes. 
       FIG. 1  illustrates components of an exemplary device that may at least partially provide and/or otherwise be included in an execution environment. The components illustrated in  FIGS. 4   a - d  may be included in or otherwise combined with the components of  FIG. 1  to create a variety of arrangements of components according to the subject matter described herein. 
       FIG. 5  illustrates user node  502  as an exemplary device that in various aspects may be included in and/or otherwise adapted for providing any of execution environments  401  illustrated in  FIGS. 4   a - c , each illustrating a different adaptation of the arrangement of components in  FIG. 3 . As illustrated in  FIG. 5 , user node  502  is operatively coupled to network  504  via a network interface component, such as network interface adapter  114 . Alternatively or additionally, an adaptation of an execution environment  401  may include and/or may otherwise be provided by a device that is not operatively coupled to a network. A server device is illustrated by application provider node  506 . Application provider node  506  may be included in and/or otherwise adapted for providing execution environment  401   d  illustrated in  FIG. 4   d . As illustrated in  FIG. 5 , application provider node  506  is operatively coupled to network  504  via a network interface component included in execution environment  401   d.    
       FIG. 4   a  illustrates execution environment  401   a  hosting application  403   a  including an adaptation of the arrangement of components in  FIG. 3 .  FIG. 4   b  illustrates execution environment  401   b  hosting browser  403   b  including an adaptation of the arrangement of components in  FIG. 3  that may operate at least partially in a network application agent  405   b  received from a remote application provider, such as network application  403   d  in  FIG. 4   d . Browser  403   b  and execution environment  401   b  may provide at least part of an execution environment for network application agent  405   b  that may be received via a network from a network application operating in a remote execution environment.  FIG. 4   c  illustrates an arrangement of the components in  FIG. 3  adapted to operate in an energy management subsystem  407   c  of execution environment  401   c . The arrangement in  FIG. 4   c  may mediate communication between applications  403   c  and one or more output devices, such as output device  130  in  FIG. 1 . 
       FIG. 4   d  illustrates execution environment  401   d  configured to host one or more network applications, such as a web service, illustrated by network application  403   d .  FIG. 4   d  also illustrates network application platform  409   d  that may provide services to one or more network applications. Network application  403   d  includes yet another adaptation of the arrangement of components in  FIG. 3 . 
     The various adaptations of the arrangement in  FIG. 3  that are described herein are not exhaustive. For example, those skilled in the art will see based on the description herein that arrangements of components for performing the method illustrated in  FIG. 2  may be at least partially included in an application and at least partially external to the application. Further, arrangements for performing the method illustrated in  FIG. 2  may be distributed across more than one node and/or execution environment. For example, such an arrangement may operate at least partially in browser  403   b  in  FIG. 4   b  and at least partially in execution environment  401   d  in and/or external to network application  403   d.    
       FIGS. 4   a - d  illustrate adaptations of network stacks  411  configured for sending and receiving messages over a network, such as network  504 , via a network interface component. Network application platform  409   d  in  FIG. 4   d  provides services to one or more network applications. In various aspects, network application platform  409   d  may include and/or interoperate with a web server.  FIG. 4   d  also illustrates network application platform  409   d  configured for interoperating with network stack  411   d.    
     Network stacks  411  may support the same protocol suite, such as TCP/IP, or may communicate via a network gateway or other protocol translation device and/or service. For example, browser  403   b  in  FIG. 4   b  and network application platform  409   d  in  FIG. 4   d  may interoperate via their respective network stacks: network stack  411   b  and network stack  411   d.    
       FIGS. 4   a - d  illustrate applications  403 , respectively, which may communicate via one or more application layer protocols.  FIGS. 4   a - d  respectively illustrate application protocol components  413  for communicating via one or more application layer protocols. Exemplary application protocols include hypertext transfer protocol (HTTP) and instant messaging and presence (XMPP-IM) protocol. Matching protocols enabling applications  403  to communicate via network  504  in  FIG. 5  are not required, if communication is via a protocol gateway or other translator. 
     In  FIG. 4   b , browser  403   b  may receive some or all of network application agent  405   b  in one or more messages sent from a network application, such as network application  403   d  via network application platform  409   d , a network stack  411 , a network interface component, and optionally an application protocol component  413 . In  FIG. 4   b , browser  403   b  includes content manager component  415   b . Content manager component  415   b  may interoperate with one or more of application protocol components  413   b  and/or network stack  411   b  to receive the message or messages including some or all of network application agent  405   b.    
     Network application agent  405   b  may include a web page for presenting a user interface for network application  403   d . The web page may include and/or reference data represented in one or more formats including hypertext markup language (HTML) and/or other markup language, ECMAScript and/or other scripting language, byte code, image data, audio data, and/or machine code. 
     In an example, in response to a request received from browser  403   b , controller component  417   d , in  FIG. 4   d , may invoke model subsystem  419   d  to perform request-specific processing. Model subsystem  419   d  may include any number of request handlers (not shown) for dynamically generating data and/or retrieving data from model database  421   d  based on the request. Controller component  417   d  may further invoke template engine  423   d  to identify one or more templates and/or static data elements for generating a user interface for representing a response to the received request.  FIG. 4   d  illustrates template database  425   d  including exemplary template  427   d .  FIG. 4   d  illustrates template engine  423   d  as a component in view subsystem  429   d  configured to return responses to processed requests in a presentation format suitable for a client, such as browser  403   b . View subsystem  429   d  may provide the presentation data to controller component  417   d  to send to browser  403   b  in response to the request received from browser  403   b . Some or all of network application agent  405   b  may be sent to browser  403   b  via network application platform  409   d  as described above. 
     While the example describes sending some or all of network application agent  405   b  in response to a request, network application  403   d  additionally or alternatively may send some or all of a network application agent to browser  403   b  via one or more asynchronous messages. In an aspect, an asynchronous message may be sent in response to a change detected by network application  403   d . Publish-subscribe protocols, such as the presence protocol specified by XMPP-IM, are exemplary protocols for sending messages asynchronously. 
     The one or more messages including information representing some or all of network application agent  405   b  in  FIG. 4   b  may be received by content manager component  415   b  via one or more of application protocol component(s)  413   b  and network stack  411   b  as described above. In  FIG. 4   b , browser  403   b  includes one or more content handler components  431   b  to process received data according to its data type, typically identified by a MIME-type identifier. Exemplary content handler components  431   b  include a text/html content handler component for processing HTML documents; an application/xmpp-xml content handler component for processing XMPP streams including presence tuples, instant messages, and publish-subscribe data as defined by various XMPP specifications; one or more video content handler components for processing video streams of various types; and still image data content handler components for processing various images types. Content handler components  431   b  process received data and may provide a representation of the processed data to one or more user interface (UI) element handler components  433   b.    
     UI element handler components  433  are respectively illustrated in presentation controller components  435  in  FIG. 4   a ,  FIG. 4   b , and  FIG. 4   c . A presentation controller component  435  may manage visual, audio, and/or other types of output of its including application  403  as well as receive and route detected user and other inputs to components and extensions of its including application  403 . With respect to  FIG. 4   b , a UI element handler component  433   b  in various aspects may be adapted to operate at least partially in a content handler component  431   b  such as a text/html content handler component and/or a script content handler component. Additionally or alternatively, a UI element handler component  433  in an execution environment  401  may operate in and/or as an extension of its including application  403 . For example, a plug-in may provide a virtual machine, for a UI element handler component received as a script and/or byte code, that may operate as an extension in application  403  and/or external to and interoperating with application  403 . 
       FIG. 6  illustrates display presentation space  602  of a display in and/or operatively coupled to user node  502 .  FIG. 6  illustrates desktop background  604  that may be a still image and/or a video background. Selection window  606  is illustrated including selectable resource icons  608 . In an aspect, a resource icon may represent image and/or video data. Resource icon  6082   b  is illustrated as selected. A selected image file and/or video stream that corresponds to a selected resource icon  608  may be processed in response to user input corresponding to operations illustrated in operation bar  610 . Selection window  606  may be a user interface presented by any of applications  403  illustrated in  FIGS. 4   a - d  and/or by network application agent  405   b . For example, selection window  606  may be presented via interoperation of browser  403   b , network application agent  405   b , and/or network application  403   d . A browser window may include a user interface of a network application provided by a remote node, such as a network application  403   d  in  FIG. 4   d.    
     Various UI elements of applications  403  described above may be presented by one or more UI element handler components  433  in  FIGS. 4   a - c  and/or by one or more template engines  423   d  in  FIG. 4   d . In an aspect, illustrated in  FIGS. 4   a - 4   c , UI element handler component(s)  433  of one or more applications  403  is/are configured to send representation information representing a visual interface element, such as operation bar  610  in  FIG. 6 , to a GUI subsystem  437 . A GUI subsystem  437  may instruct a graphics subsystem  439  to draw the visual interface element in a region of display presentation space  602 , based on representation information received from a corresponding UI element handler component  433 . 
     Input may be received corresponding to a UI element via an input driver  441  illustrated in  FIGS. 4   a - c  in various adaptations. For example, a user may move a mouse to move a pointer presented in a display presentation space  602  over an operation user interface element presented in an operation bar  610 . A user may provide an input detected by the mouse. The detected input may be received by a GUI subsystem  437  via an input driver  441  as an operation or command indicator based on the association of the shared location of the pointer and the operation user interface element in display presentation space  602 . 
     With reference to  FIG. 2 , block  202  illustrates that the method includes detecting a change in a first energy source during processing of a first resource by a program component. Accordingly, a system for selecting a resource in response to a change in available energy includes means for detecting a change in a first energy source during processing of a first resource by a program component. For example, as illustrated in  FIG. 3 , energy monitor component  302  is configured for detecting a change in a first energy source during processing of a first resource by a program component.  FIGS. 4   a - d  illustrate energy monitor components  402  adaptations and/or analogs of energy monitor component  302  in  FIG. 3 . One or more energy monitor components  402  operate an in execution environment  401 . 
       FIG. 4   a  illustrates energy monitor component  402   a  operating in application  403   a . Energy monitor component  403   a  may monitor an energy source, directly and/or indirectly, while application  403   a  processes a first resource.  FIG. 4   b  illustrates energy monitor component  402   b  operating in network application agent  405   b . Network application agent  405   b  may operate in user node  502 . Network application agent  405   b  may be received by user node  502  from network application  403   d  operating in application provider node  506 . Energy monitor component  402   b  may monitor an energy source while a first resource is processed by network application agent  405   b , browser  403   b , and/or network application  403   d . Energy monitor component  402   b  may monitor an energy source providing energy to one or more hardware components included in execution environment  401   b  and/or may monitor an energy source providing energy to one or more hardware components included in execution environment  401   d . Alternatively or additionally, energy monitor component  402   d  may monitor an energy source for user node  502  and/or application provider node  506  while a first resource is processed by one or both of network application agent  405   b  and/or network application  403   d .  FIG. 4   c  illustrates energy monitor component  402   c  operating in energy management subsystem  407   c . Energy monitor component  402   c  may monitor an energy source for execution environment  401   c  while one or more applications  403   c  process respective resources. 
     Detecting a change in a first energy source may include receiving and/or otherwise detecting energy from the first energy source and subsequently receiving and/or otherwise detecting energy from a second energy source. Energy from the second energy source may be received along with energy from the first energy source. In another aspect, the change may include receiving energy from the second energy source rather than receiving energy from the first energy source. For example, energy monitor component  402   c  in  FIG. 4   c  may detect a change in receiving energy from an electrical outlet to receiving energy from a battery (not shown) in execution environment  401   c.    
     Detecting a change in a first energy source may include detecting a change in an amount of energy available and/or a rate of energy receivable from a first energy source. An rate of energy receivable may include an amount of energy that may be received in a particular time period. An amount of energy available may include an amount of stored energy as measured by a specified metric. For example, energy monitor component  402   a  in  FIG. 4   a  may detect that a first hardware component is receiving energy at a rate above a specified threshold, then detect that the first hardware component is receiving energy at or below the threshold. The change may be in response to a detectable change in activity in the first hardware component and/or in a second hardware component. Energy monitor component  402   a  may monitor the energy source by monitoring activity in one or more hardware components. 
     Detecting a change in an amount and/or rate of energy may include detecting energy flowing to an energy source. In another example, energy monitor  402   b  in  FIG. 4   b  may detect a change in a flow of energy from an energy source, such as a battery, to a net flow of energy to the energy source, for example, indicating that the battery is charging. 
     Detecting a change in an energy source may include detecting a change in an attribute of the energy source. Detecting a change in an energy source may include and/or otherwise may be based on a change in a receiver of energy, in a monetary cost of energy, in an organization providing energy, in a rate of energy utilization, in a utilization time of an energy source, in a user, in a geospatial location, in heat, in light, and/or in a change in a component for at least one of storing, transmitting, and receiving energy. For example, in  FIG. 4   d , energy monitor component  402   d  may receive event information identifying one or more events and/or conditions indicating a change. Energy monitor component  402   d  may receive event information for an energy source for a remote device, such as user node  502  hosting network application agent  405   b , and/or for an energy source for execution environment  401   d  including and/or otherwise provided by application provider node  506 . 
     Returning to  FIG. 2 , block  204  illustrates that the method further includes selecting a second resource based on a second measure of an energy cost for processing the second resource. Accordingly, a system for selecting a resource in response to a change in available energy includes means for selecting a second resource based on a second measure of an energy cost for processing the second resource. For example, as illustrated in  FIG. 3 , cost monitor component  304  is configured for selecting a second resource based on a second measure of an energy cost for processing the second resource.  FIGS. 4   a - d  illustrate cost monitor components  404  as adaptations and/or analogs of cost monitor component  304  in  FIG. 3 . One or more cost monitor components  404  operate in an execution environment  401 . 
     A cost monitor component  404  in  FIGS. 4   a - d  may determine and/or otherwise identify a metric for an energy source for measuring an energy cost for processing a resource. Measures of an energy cost may be determined for a number of resources. 
     In an aspect, an energy condition and/or or other cost condition may be evaluated based on a measure of energy and/or a measure of another type of processing cost for a resource. Resource locator component  404  may determine the type of energy cost and/or other processing cost and/or may determine the measure. 
     A resource may be selected automatically based on a measure of an energy and/or other processing cost in response to detecting a change in an energy source. In another aspect, one or more resources may be identified and a resource in the identified resources may be selected in response to a user input detected by an input device. 
     A metric defines a unit of measure. For example, an “inch” is a unit of measure for measuring length. A “kilowatt-hour” (kWh) is a unit of measurement defined by a metric for measuring an amount of energy. Instead of or in addition to measuring an amount a metric may measure a rate. “Kilowatts per hour” (kWh/h) is an energy or a power metric for measuring a rate of energy used. A “measure” is a result of a particular measuring or measurement process. For example, 3 inches is a measure according to the length metric for inches, and 1000 kWh is a measure of an energy metric identifying an amount of energy. As used herein, a “measure of a processing cost” refers to a result of a measuring process for determining a processing cost according to a specified metric. Thus, a measure of an energy cost refers to a result of a measuring process for determining an energy cost according to a specified metric. Measuring may include estimating a measurement. 
     Metrics for determining measures of energy cost include kilowatt-hours, kilowatts per hour; money spent for energy utilized; and changes in heat due to energy utilized measured, for example, according to the Celsius scale, to name a few examples. 
     A processing cost may be determined and/or expressed by any metric, directly and/or indirectly, providing an indication of a cost associated with processing a resource in performing a specified operation. An energy cost provides an indication of an energy cost associated with processing a resource. A metric for determining an energy cost in terms of electrical energy may be determined by monitoring and measuring a flow of electricity over time to a hardware component that is included in processing a resource. For example, a flow of electricity to a network interface adapter may be monitored for resources where processing the resources by a program component includes sending and/or receiving data via a network. Some of the data may be included in the resources. The metric may represent the cost, for example, in kilowatt-hours, in transmission time, in bandwidth utilization, in latency, and/or in monetary units. In  FIGS. 4   a - d , cost monitor component  404  may be configured to determine and/or otherwise identify a measure of an energy cost and/or other processing cost for a resource in selecting a resource. 
     A metric may be specified for measuring and expressing an energy cost and/or other processing cost in a less direct manner. For example, with respect to energy cost, an energy cost may be measured by counting occurrences of an energy consuming activity, such as a disk read. From another perspective a metric based on disk reads may be a direct measure of a utilization cost resulting from processing one or more resources stored in a hard drive. 
     Exemplary metrics for measuring an energy cost and/or other processing cost include metrics for energy, monetary metrics, time metrics, kinetic or stored energy metrics, heat metrics, resistance including mechanical and/or electrical resistance, metrics for measuring various energy and/or energy consuming activities, metrics for measuring an environmental cost, health metrics, safety metrics, light metrics, metrics for measuring movement, metrics for measure mass and/or weight, and/or metrics for measuring an opportunity cost. 
     A particular metric for determining a measure of an energy cost and/or other processing cost for a resource may be selected and/or otherwise identified based on one or more attributes of a resource, an operation that includes processing the resource, a program component for performing some or all of the operation, a hardware component included in processing the resource, a user, an organization, an energy source, and/or a task, to name a few examples. For example, a metric such as a count of machine code instructions executed by an IPU may be specified and/or determined in performing a specified operation. An IPU based metric may be selected for measuring a cost of processing a resource where no output device is included in processing the resource. For an application or process that presents a user interface via a display component included in presenting visual output to a user, a metric for measuring heat and/or light generated by the display device may be specified. 
     A cost monitor component  404 , in an aspect, may determine a measure of an energy cost and/or other processing cost based on metadata provided in and/or with a resource, a program component for performing an operation that includes processing the resource, and/or a hardware component included in performing an operation that includes processing the resource. A measure of an energy cost and/or other processing cost may be predetermined and identified by cost monitor component  404  in and/or associated with a resource, a program component, and/or a hardware component. 
     A cost monitor component  404  may look up and/or may otherwise identify a predefined value for a resource based on a type of the resource, a size of the resource, an energy source, a hardware component, and/or a program component for processing the resource. The predefined value may be a measure of an energy cost and/or other processing cost, and/or may be an input for determining a measure of an energy cost and/or other processing cost expressed according to an identified metric. For example, a predefined value may be multiplied by a measure of time that a resource may be processed by a program component to produce a time based metric such as kilowatt-hours or disk reads per minute. 
     In another aspect, a cost monitor component  404  may determine a measure of an energy cost and/or other processing cost by calculating the measure according to the specified metric and/or may interoperate with a sensor, such as thermometer, in measuring a cost. Cost monitor component  404  may include and/or otherwise access one or more measurement components for determining a measure according to one or more metrics. 
     Cost monitor component  404   a  is illustrated operating in application  403   a  in  FIG. 4   a . Cost monitor component  404   a  may determine a measure of an energy cost and/or other processing cost for resources processed by application  403   a . The resources may include resources provided by application  403   a  to other applications, subsystems, and/or components operating in execution environment  401   a  and/or in another execution environment included in and/or otherwise provided by one or more devices. 
     For example, application  403   a  may present selection window  606  in  FIG. 6  in response to detecting a change in an energy source. The resources processed by application  403   a  may be represented by resource icons  608 . The resources may include data to send to another node. Cost monitor component  404   a  may determine a measure of an energy cost and/or other processing cost for transmitting the data to the other node via a network adapter in execution environment  401   a . The transmission may be via physical network media physically coupled to the network adapter. For example, cost monitor component  404   a  may determine a measure based on a count of bytes of data in the resources and/or in an encoded translation of the resource(s) for transmitting. Resources selected for presentation may be represented by resource icons  608 . 
     In  FIG. 4   b , cost monitor component  404   b  is illustrated operating in network application agent  405   b . Network application agent  405   b  may be received by browser  403   b  operating in user node  502  in  FIG. 5  from network application  403   d  in  FIG. 4   d  operating in application provider node  506  in  FIG. 5  as described above.  FIG. 4   d  illustrates cost monitor component  404   d  operating in network application  403   d . Cost monitor component  404   b  and/or cost monitor component  404   d  may determine a measure of an energy cost and/or other processing cost for a resource processed by network application  403   d  and/or network application agent  405   b . Cost monitor component  404   b  and/or cost monitor component  404   d  may be components in a cost monitoring system distributed between network application agent  405   b  and network application  403   d . Cost monitor component  404   b  and/or cost monitor component  404   d  may operate independently. Operating independently may include operating in the absence of the other cost monitor component. Resources selected may include resources provided by network application agent  405   b  to browser  403   b  and/or extensions of browser  403   b . The resources may further include resources selected to provide to other nodes in network  504  by network application agent  405   b  and/or network application  403   d . Selecting a resource may include network application agent  405   b  interoperating with browser  403   b  to present selection window  606  in  FIG. 6  in a browser window or tab (not shown). The selected resources may be represented by resource icons  608 . 
     Cost monitor component  404   b  and/or cost monitor component  404   d  may determine a measure of an energy cost and/or other processing cost in selecting one or more resources where processing the resources includes transmitting the resources via network  504  in  FIG. 5 . Transmitting resource data may include encoding, decoding, filtering, translating, and/or transforming some or all of the data in a resource in some manner. For example, a resource may be compressed prior to transmitting via network  504 . Cost monitor component  404   b  may be configured to determine a metric based on a type of physical layer network included in network  504 , based on an encoding, decoding, and/or other transformation, based on a manufacturer and/or type of network interface component, and/or based on network throughput data and/or other network attributes. The measure may be a cost for transmitting a web document via a network via a modem, a cost for retrieving image data in the document from a hard drive, a cost for decoding data received via network  504 , and/or a cost for transmitting data over a secure network connection. Cost monitor component  404   b  and/or cost monitor component  404   d  may be configured with and/or otherwise may identify a predefined measure of an energy cost and/or other processing cost according to a metric selected by a developer of browser  403   b.    
     In  FIG. 4   c , cost monitor component  404   c  is illustrated operating in energy management subsystem  407   c . Energy management subsystem  407   c  may be a subsystem of execution environment  401   c  that provides services to a number of program components in execution environment  401   c  and/or in another execution environment communicatively coupled via network  504  in  FIG. 5 . Cost monitor component  404   c  may select one or more resources in response to a change in an energy source based on respective measures of an energy cost and/or other processing cost(s) for various resources processed by various applications  403   c  operating in execution environment  401   c . In another aspect, cost monitor component  404   c  may select one or more resources prior to a change in an energy source. The resources may include resources provided to and/or otherwise accessible to applications  403   c  via various subsystems of execution environment  401   c , such as a file system (not shown) and/or network stack  411   c.    
     For example, selection window  606  in  FIG. 6  may be presented as a document navigation window presented by execution environment  401   c . “Op 1 ” presented in operation bar  610  may invoke application  403   c   1  for processing a currently selected resource, illustrated as resource icon  6082   b . “Op 2 ” in operation bar  610  may be a user interface control for invoking application  403   c   2  for one or more selected resources represented by resource icons  608 . The resources processed by application  403   c   1  may include documents having various content types. Cost monitor component  404   c  may determine a measure of an energy cost and/or other processing cost for the documents expressed by a metric based on the format of the respective documents identified by content type and based on an operation for processing the documents. The operation may be performed by application  403   c   1  and/or may be performed by one or more other components. 
     For example, for a particular device a file system operation may be configured to be an operation for determining a measure of an energy cost and/or other processing cost for a resource processed by application  403   c   1 . In  FIG. 4   c , energy management subsystem  407   c  may determine energy cost and/or other processing costs for resources, freeing applications  403   c  from performing this operation. Note that in an aspect; at least some of energy management subsystem  407   c  may operate in a node other than the node included in and/or providing execution environment  401   c . For example, some or all of the arrangement of components may be adapted to operate in execution environment  401   d , which includes and/or is otherwise provided by application provider node  506 . 
     Cost monitor component  404   a  is illustrated operating in application  403   a . Cost monitor component  404   a  may determine a measure of an energy cost and/or other processing cost for resources processed by application  403   a . Application  403   a  is a program component and may include one or more program components. The resources may include resources provided by application  403   a  to other applications, subsystems, and/or components operating in execution environment  401   a  and/or in another execution environment included in and/or otherwise provided by one or more devices. For example, application  403   a  may present selection window  606  in  FIG. 6  to select resources to identify to a program component in response to a change in an energy source. The resources selected by application  403   a  may include images and videos represented by icons  608 . Cost monitor component  404   a  may determine a measure of an energy cost and/or other processing cost for presenting the images and/or videos as desktop backgrounds. For example, cost monitor component  404   a  may be configured with and/or otherwise may determine a measure based on a count of display refreshes over a specified period of time for the various resources to determine a measure of an energy cost and/or other processing cost for presenting the various respective resources. Cost monitor component  404   a  may select and/or otherwise identify resources for presenting in selection window  606  based on a measure of an energy cost and/or other processing cost. 
     In an aspect, a resource may be selected and/or otherwise identified based on selection information received in response to a user input detected by an input device and based on a measure of an energy cost and/or other processing cost. The measure and/or an indication based on the measure may be presented for respective resources available for processing by a particular program component. For example, application  403   a  in  FIG. 4   a  may be processing a first resource and may present a user interface for identifying another resource in response to a change detected in an energy source. 
     For example, cost monitor component  404   a  in  FIG. 4   a  may send presentation information to present a cost indication for one or more resources presented in selection window  606  in  FIG. 6 , allowing a user to select a resource represented by a particular resource icon  608  from the resources represented by respective resource icons. Selection input from a user identifying a resource represented by the particular icon may be received based on a cost indication presented for the resource in response to a detected change in an energy source. The cost indication is based on a measure of an energy cost and/or other processing cost for the resource. 
     A user input selecting a resource for processing by the application may be detected by a UI element handler  433   a  for the selection user interface and/or for the representation of the resource. In an aspect, cost monitor component  404   a  may determine whether to send presentation information to present a cost indication for a resource based on an energy condition. For example, cost monitor component  404   a  may evaluate a specified energy condition based on a determined measure of an energy cost and/or other processing cost for a resource. When the energy condition is met, cost monitor component  404  may select one or more resources for processing and send presentation information for presenting the resources in the selection user interface. When the condition is not met, the resource is not selected for presenting. In the aspect, only resources that meet a particular energy condition and/or other cost condition may be selected for identifying for processing. For example, in  FIG. 6 , normally presented icons  608  may be presented as selectable as directed by cost monitor component  404 . Patterned icons such as icon  608   mb  may be presented as non-selectable by a cost monitor component  404 , so that user input corresponding to icon  608   mb  is not processed as a selection of the resource as analogous input for normally presented icons is processed as a selection. 
     A cost monitor component  404  may change or otherwise provide for changing a pointing device representation, such as a mouse pointer, when it approaches and/or is in a location of a presented resource, as a cost indication based on a measure according to a particular metric for processing a resource represented by a UI element in the location. For example, different colors of the pointer may be defined as different cost indications associated with different measures of an energy cost and/or other processing cost. Alternatively or additionally, a pointer may be deactivated for selecting a resource based on a measure of an energy cost and/or other processing cost for the resource. In an aspect, a resource may be automatically selected when an energy condition based on a measure of an energy cost and/or other processing cost is met in response to a change in an energy source. 
     In  FIG. 4   d , cost monitor component  404   d  in network application  403   d  may send information via a response to a request and/or via an asynchronous message to a client, such as browser  403   b  and/or network application agent  405   b , to present a user detectable indication of a measure of an energy cost and/or other processing cost for a resource. One or more resources may be selected for representing based on their respective measures and/or corresponding cost indications. 
     Presentation information for presenting a cost indication may be sent in a message via a network to a node operatively coupled to an output device. Cost monitor component  404   d  in  FIG. 4   d  operating in application provider node  506  in  FIG. 5  may send presentation information in response to a request from network application agent  405   b  in  FIG. 4   b  operating in user node  502 . 
     A change in an energy source may be detected while a resource is being processed. In response to one or more detected changes, an alternative and/or an additional resource may be selected for respectively being identified to a program component instead of and/or in addition to the resource currently being processed. 
     For example, energy management subsystem  407   c  in  FIG. 4   c  may monitor a level of energy in a battery providing energy for a handheld device. Energy management subsystem  407   c  may invoke cost monitor component  404   c  in response to detecting a battery energy level fall below a specified threshold. Cost monitor component  404   c  may recalculate and/or otherwise determine a measure of an energy cost and/or other processing cost for one or more resources in response to the change in battery state. Cost monitor component  404  may locate and/or otherwise select an alternative and/or an additional resource depending on the change. 
     In an aspect, an energy condition may be specified. A measure of an energy cost and/or other processing cost may be determined for evaluating an energy condition to determine whether the energy condition is met for a resource. An energy condition may be identified for evaluating and/or may be evaluated based on a change in an energy source including a change in an amount of energy available, an amount of energy available in a battery and/or other energy store, an amount of energy used and/or currently being used for processing another resource, a location of the device, and/or a time required for restoring an energy store to a specified state, to name a few examples. 
     When an energy condition is not met for a resource, a cost monitor component  404  may select and/or locate one or more alternative resources to a first resource based on one or more respective measures of an energy cost and/or other processing cost determined by the cost monitor component  404 . One or more representations of the respective one or more alternative resources may be selected for presenting to a user. A user input may be received from the user for selecting an alternative resource. A user input may be received indicating that the first resource is to be provided to the program component for processing. In yet another alternative, a cost monitor component  404  may automatically select an alternative resource that meets the energy condition for processing instead of the first resource. In an additional aspect, the first resource may meet the energy condition and cost monitor component  404  may select one or more resources from the alternatives to identify to the program component in addition to the first resource. Resource director component  406  may identify the additional resources automatically and/or may receive input from a user to identify one or more additional resources. 
     Returning to  FIG. 2 , block  206  illustrates that the method yet further includes identifying the second resource to the program component for processing in response to detecting the change. Accordingly, a system for selecting a resource in response to a change in available energy includes means for identifying the second resource to the program component for processing in response to detecting the change. For example, as illustrated in  FIG. 3 , resource director component  306  is configured for identifying the second resource to the program component for processing in response to detecting the change.  FIGS. 4   a - d  illustrate resource director components  406  as adaptations and/or analogs of resource director component  306  in  FIG. 3 . One or more resource director components  406  operate in an execution environment  401 . 
     As described above, a resource may be identified in response to detecting a user input for selecting the resource. Selection information may be received by a UI element handler component  433  for a selectable representation of a resource. The UI element handler component  433  receiving the selection information may provide and/or otherwise identify the resource to a resource director component  406  in response to a change detected in an energy source. A resource director component  406  may access the resource, transform the resource into a format suitable for processing by the program component, and/or identify the resource to the program component for processing. 
     In  FIG. 4   a , resource director component  406   a  may identify a resource, in response to a change detected in an energy source, to any one or more components in application  403   a . In  FIG. 4   b  and/or in  FIG. 4   d , resource director component  406   b  and/or resource director component  406   d  may identify a selected resource to any one or more components in browser  403   b  and/or to network application agent  405   b . Resource director component  406   b  and resource director component  406   d  may operate alone without the presence of the other, may operate independently while the other is operating or is not operating, or may interoperate to identify the selected resource in various aspects. In  FIG. 4   c , resource director component  406   c  may identify a resource selected based on a measure of an energy and/or other processing cost, in response to a change detected in an energy source, to any of one or more program components including various applications  403   c . Alternatively or additionally, resource director component  406   c  may identify a selected resource to a program component operating in another execution environment including and/or otherwise provided by another node. 
     Also as described above, a resource may be identified automatically, in response to being selected and/or in response to detecting a change in an energy source. A program component may be performing an operation that includes processing a first resource. A second resource may be identified based on a measure of an energy cost, in response to a change detected in an energy source, to the program component to perform the operation instead of the first resource. For example, application  403   a  in  FIG. 4   a  operating in a user device, such as user node  502  in  FIG. 5 , may present a resource as desktop background  604  in  FIG. 6 . When user node  502  is operating on a battery with an estimated energy available exceeding a specified time threshold, such as one hour, resource director component  406   a  may identify a video resource, selected by cost monitor component  404   a , to present in display presentation space  602  as desktop background  604  based on a measure of an energy cost and/or other processing cost determined for the video resource. When a change in an energy source is detected in user node  502  where user node  502  is operating on a battery with an estimated energy available that is less than a specified time threshold, such as one hour, resource director component  406   a  may identify a still image resource, selected by cost monitor component  404   a , to present in display presentation space  602  as desktop background  604  where a measure of the energy cost and/or other processing cost for the still image meets an energy condition based on the energy available in the battery and the video does not meet the condition. 
     In another aspect, a program component may be performing an operation that includes processing a first resource. A second resource, selected based on a measure of an energy cost and/or other processing cost for the resource, may be identified to the program component to perform the operation in addition to performing the operation including processing the first resource. For example, network application agent  405   b  in  FIG. 4   b  operating in user node  502  may upload files to network application  403   d  operating in application provider node  506  via network  504 . When network  504  is a public network and a public energy supply is providing energy with no monetary charge to a user of user node  502  for energy utilized for transmitting data via the network, a measure based on a metric of the monetary cost of bandwidth may be zero or near zero for resources to transfer from user node  502  to application provider node  506 . A user may select a first resource for upload. Based on the bandwidth cost, resource director component  406   b  may select and identify an additional resource to transmit from user node  502  to application provider node  506  to transfer in parallel with the first resource. Alternatively or additionally, resource director component  406   d  may send a matching criterion to identify one or more additional resources to receive in parallel with the first resource from network application agent  405   b  operating in browser  403   b.    
     As described herein, a resource may be selected based on a measure of an energy cost and/or other processing cost. In an aspect, at some time after the resource is selected, the resource may be identified to a program component in response to the detection of a specified event. A number of resources may be selected. The resources may be associated with a number of respective detectable changes associated with an energy source. In response to a first detected change, a second resource may be identified to a program component. In  FIG. 4   c , energy management subsystem  407   c  may change permissions, roles, etc. for selected resources in response to a detected change in an energy source. The change in permissions, roles, etc. may allow access to and/or otherwise identify resources that match and/or otherwise meet an energy condition. 
     The method illustrated in  FIG. 2  may include additional aspects supported by various adaptations and/or analogs of the arrangement of components in  FIG. 3 . In an aspect, detecting a change in an energy source may include detecting a change in energy available from a first energy source and configuring an amount of energy received from a second energy source. Prior to detection of the change, one or both of the energy sources may be actively providing energy. In a further aspect, detecting an amount of energy available from an energy source may include detecting an amount of energy stored in the energy source. For example, energy monitor component  402   c  in  FIG. 4   c  may determine that a measure of stored energy in a first battery is below a specified threshold. In response, energy management subsystem  407   c  may configure one or more components in execution environment  401   c  to receive energy and/or to receive additional energy from a second battery. When energy monitor component  402   c  determines that a measure of stored energy in a first battery exceeds a specified threshold, energy management subsystem  407   c  may stop or decrease an amount of energy being received from the second battery for operating the one or more components in execution environment  401   c.    
     In an aspect, detecting a change in an energy source may include detecting energy flowing from a first energy source providing energy to a hardware component in an execution environment, and subsequently detecting a net flow of energy to the energy source. An energy monitor component  402  in  FIGS. 4   a - d  may detect when a battery is charging and/or providing energy for operating a component in an execution environment  401 . 
     Detecting a change in an energy source may include determining a first energy condition prior to the change and determining a second energy condition based on the change. An energy condition may be determined based on a measure of an energy cost for processing a resource by a program component. Browser  403   b  in  FIG. 4   b  may receive network application agent  405   b  as a resource for processing and/or including a resource for processing. Processing network application agent  405   b , including receiving network application agent  405   b  via network  504 , may change an energy condition based on a measure of an energy cost determined by cost monitor component  404   c  and/or cost monitor component  404   d  in  FIG. 4   d.    
     Also as described above, a resource may be selected based on at least one of at least a portion of an identifier of the first resource, a file type, a record type, a content type, and a program component. 
     As described above, selecting a resource may include determining a measure of an energy cost. A measure of an energy cost may be determined and/or expressed based on at least one of volts, watts, amps, a measure of energy, a measure of mechanical resistance, a measure of electrical resistance, a measure of time, a count of a particular activity, a measure of heat, and measure of light. 
     A measure of an energy cost may include a measure of electrical energy, a measure of stored energy, a measure of mechanical resistance, a measure of electrical resistance, a measure of time, a count of a particular event, a measure of monetary cost, a measure of heat, a measure of light, a measure of distance, a measure of mass, a measure of size, and/or a measure of weight. A count may be based on CPU cycles, disk spins, data read operations, data write operations, refreshes of at least a portion of a presentation space, display refreshes, data transmitted via a network, data received via a network, and/or a measure of human movement. 
     A metric for measuring an energy cost and/or other processing cost may be determined and/or otherwise identified based on at least one of a resource, an operation, a hardware component, a program component, a user, a group, a role, a task, a time, a location, and a device for performing an operation and/or for providing a resource. A user input may be received identifying a metric for determining a measure. 
     Determining a measure of an energy cost and/or other processing cost may be based on a previous determination of a measure of an energy cost and/or other processing cost. A past measure may be included in determining a current measure. A measure of an energy cost may be predetermined and retrieved as needed by a cost monitor component  404  in  FIGS. 4   a - d . Alternatively or additionally, a measure of an energy cost may be measured by a cost monitor component  404 , directly and/or indirectly, on demand. For example, a cost monitor component  404  may measure an energy cost in response to a change detected in an energy source. The measuring may be performed automatically in response to the detected change. 
     Selecting a resource may include comparing a first measure of an energy cost for processing the resource with a second measure for a second resource; and selecting the second resource based on a result of the comparing. Cost monitor component  404   a  in  FIG. 4   a  may determine a first measure for a first resource being processed by a program component and may determine a second measure for a second resource. Cost monitor component  404   a  may select the second resource by comparing the first measure and the second measure. The second measure may be greater than, equal to, or less than the first measure. Selecting the second resource may further be based on the detected change as described above. 
     As described above, determining a measure of an energy cost and/or other processing cost may include sending a message via a network to a node for determining at least one of the first measure and the second measure, and receiving a response via the network identifying the measure. 
     Selecting a resource may include communicating with a presentation device to present a selectable representation of a second resource to a user. Selection information may be received identifying the second resource, in response to a detected user input. The second resource may be selected in response to receiving the selection information. A user may select the second resource based on energy cost information presented in the user interface. 
     Identifying a selected resource to a program component may include disabling access, for the program component, to a resource currently being processed, and enabling access, for the program component, to the selected resource. In  FIG. 4   d , resource director component  406   d  may change access information, disabling user node  502  and/or browser  403   b  from accessing and/or continuing to access a first resource currently being processed by user node  502 . Resource director component  406   d  may disable access to one or more other resources based on respective measures of energy cost and/or other processing cost. To identify a selected resource, resource director component  406   d  may interoperate with an access control component to enable access to a second resource enabling user node  502  and/or browser  403   b  to access the identified resource. 
     Identifying a selected resource to a program component may include terminating the program component and subsequently starting the program component configured to process the selected resource. In  FIG. 4   c , resource director component  406   c  may terminate a computing process in which first application  403   c   1  processes a first resource. Resource director component  406   c  may initiate a new computing process in which first application  403   c   1  may operate. Resource director component  406   c   1  may identify a second resource for processing by identifying the second resource as an input to the new computing process. 
     To the accomplishment of the foregoing and related ends, the descriptions and annexed drawings set forth certain illustrative aspects and implementations of the disclosure. These are indicative of but a few of the various ways in which one or more aspects of the disclosure may be employed. The other aspects, advantages, and novel features of the disclosure will become apparent from the detailed description included herein when considered in conjunction with the annexed drawings. 
     It should be understood that the various components illustrated in the various block diagrams represent logical components that are configured to perform the functionality described herein and may be implemented in software, hardware, or a combination of the two. Moreover, some or all of these logical components may be combined, some may be omitted altogether, and additional components may be added while still achieving the functionality described herein. Thus, the subject matter described herein may be embodied in many different variations, and all such variations are contemplated to be within the scope of what is claimed. 
     To facilitate an understanding of the subject matter described above, many aspects are described in terms of sequences of actions that may be performed by elements of a computer system. For example, it will be recognized that the various actions may be performed by specialized circuits or circuitry (e.g., discrete logic gates interconnected to perform a specialized function), by program instructions being executed by one or more instruction-processing units, or by a combination of both. The description herein of any sequence of actions is not intended to imply that the specific order described for performing that sequence must be followed. 
     Moreover, the methods described herein may be embodied in executable instructions stored in a computer readable medium for use by or in connection with an instruction execution machine, system, apparatus, or device, such as a computer-based or processor-containing machine, system, apparatus, or device. As used here, a “computer readable medium” may include one or more of any suitable media for storing the executable instructions of a computer program in one or more of an electronic, magnetic, optical, electromagnetic, and infrared form, such that the instruction execution machine, system, apparatus, or device may read (or fetch) the instructions from the computer readable medium and execute the instructions for carrying out the described methods. A non-exhaustive list of conventional exemplary computer readable media includes a portable computer diskette; a random access memory (RAM); a read only memory (ROM); an erasable programmable read only memory (EPROM or Flash memory); optical storage devices, including a portable compact disc (CD), a portable digital video disc (DVD), a high definition DVD (HD-DVD®, and a Blu-ray® disc; and the like. 
     Thus, the subject matter described herein may be embodied in many different forms, and all such forms are contemplated to be within the scope of what is claimed. It will be understood that various details may be changed without departing from the scope of the claimed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation, as the scope of protection sought is defined by the claims as set forth hereinafter together with any equivalents. 
     All methods described herein may be performed in any order unless otherwise indicated herein explicitly or by context. The use of the terms “a” and “an” and “the” and similar referents in the context of the foregoing description and in the context of the following claims are to be construed to include the singular and the plural, unless otherwise indicated herein explicitly or clearly contradicted by context. The foregoing description is not to be interpreted as indicating that any non-claimed element is essential to the practice of the subject matter as claimed.