Abstract: A distributed, web-services based storage system. A system may include a web services interface configured to receive, according to a web services protocol, a given client request for access to a given data object, the request including a key value corresponding to the object. The system may also include storage nodes configured to store replicas of the objects, where each replica is accessible via a respective unique locator value, and a keymap instance configured to store a respective keymap entry for each object. For the given object, the respective keymap entry includes the key value and each locator value corresponding to replicas of the object. A coordinator may receive the given client request from the web services interface, responsively access the keymap instance to identify locator values corresponding to the key value and, for a particular locator value, retrieve a corresponding replica from a corresponding storage node.

Abstract: A distributed, web-services based storage system. A system may include a web services interface configured to receive, according to a web services protocol, a given client request for access to a given data object, the request including a key value corresponding to the object. The system may also include storage nodes configured to store replicas of the objects, where each replica is accessible via a respective unique locator value, and a keymap instance configured to store a respective keymap entry for each object. For the given object, the respective keymap entry includes the key value and each locator value corresponding to replicas of the object. A coordinator may receive the given client request from the web services interface, responsively access the keymap instance to identify locator values corresponding to the key value and, for a particular locator value, retrieve a corresponding replica from a corresponding storage node.

Abstract: A distributed, web-services based storage system. A system may include a web services interface configured to receive, according to a web services protocol, a given client request for access to a given data object, the request including a key value corresponding to the object. The system may also include storage nodes configured to store replicas of the objects, where each replica is accessible via a respective unique locator value, and a keymap instance configured to store a respective keymap entry for each object. For the given object, the respective keymap entry includes the key value and each locator value corresponding to replicas of the object. A coordinator may receive the given client request from the web services interface, responsively access the keymap instance to identify locator values corresponding to the key value and, for a particular locator value, retrieve a corresponding replica from a corresponding storage node.

Abstract: A distributed, web-services based storage system. A system may include a web services interface configured to receive, according to a web services protocol, a given client request for access to a given data object, the request including a key value corresponding to the object. The system may also include storage nodes configured to store replicas of the objects, where each replica is accessible via a respective unique locator value, and a keymap instance configured to store a respective keymap entry for each object. For the given object, the respective keymap entry includes the key value and each locator value corresponding to replicas of the object. A coordinator may receive the given client request from the web services interface, responsively access the keymap instance to identify locator values corresponding to the key value and, for a particular locator value, retrieve a corresponding replica from a corresponding storage node.

Abstract: A distributed storage system including support for distinct storage classes. A system may implement a web services interface, a number of storage nodes and a coordinator. The web services interface may receive, according to a web services protocol, client requests to store data objects. A request for a given object may include an indication of a particular storage class to be associated with the given object, and where each storage class respectively specifies one or more service level agreement (SLA) characteristics. The storage nodes may store replicas of the data objects. The coordinator may receive the client requests to store the data objects from the web services interface, where in response to the given client request, the coordinator may store one or more replicas of the given data object among the storage nodes according to the SLA characteristics specified by the particular storage class.

Abstract: A distributed, web-services based storage system. A system may include a web services interface configured to receive, according to a web services protocol, a given client request for access to a given data object, the request including a key value corresponding to the object. The system may also include storage nodes configured to store replicas of the objects, where each replica is accessible via a respective unique locator value, and a keymap instance configured to store a respective keymap entry for each object. For the given object, the respective keymap entry includes the key value and each locator value corresponding to replicas of the object. A coordinator may receive the given client request from the web services interface, responsively access the keymap instance to identify locator values corresponding to the key value and, for a particular locator value, retrieve a corresponding replica from a corresponding storage node.

Abstract: An injection molding machine is provided including a first mold portion and a second mold portion, the second mold portion being movable relative to the first mold portion and together defining a mold cavity. The injection molding machine includes a fluid path extending through the first mold portion. The fluid path has an inlet fan gate portion in fluid communication with the mold cavity. The injection molding machine further includes a valve device disposed in the fan gate portion directly adjacent the mold cavity. The valve device is positionable in an opened position to permit flow of the molding material from the fan gate portion to the mold cavity and a closed position to obstruct flow of the molding material from the fan gate portion to the mold cavity. In the closed position, the valve device defines a wall surface portion for forming the molded part and thereby eliminating the need for a post-machining operation to remove the gate portion.

Abstract: Content is authenticated by generating signature certificates for content that has been successfully watermark screened. When a request is received for importation of content into a secured domain, a search is made in a signature certificates cache for a signature certificate associated with that requested content. If an identified signature certificate authenticates the requested content, the content is imported into the secured domain. If no signature certificate is identified, the content is watermark screened. If the content successfully passes the watermark screening process, a new signature certificate is then added to the signature certificate cache.

Abstract: A portable device receives content from a computer and a signature certificate. The signature certificate is derived from content after the content successfully passes a watermark screening process. The portable device compares the received signature certificate to the received content. The content is only played in the portable device when the received signature certificate authenticates the received content as passing the watermark screening process.

Abstract: The present invention provides a method and apparatus for a scheduling driver to implement a protocol using time estimates for use with a device that does not generate interrupts. An application calls the scheduling driver to start an Input/Output (I/O) request to a device. The scheduling driver determines if the device is busy. If the device is not busy, the scheduling driver provides an estimated processing time (EPT) for the I/O request to be completed to the application. In one embodiment, if the device is busy, the scheduling driver calculates an estimated amount of time left (EATL) until the device will be available to the application and provides this EATL to the application. When the device is not busy, the application sleeps for the estimated processing time (EPT) and calls the scheduling driver to obtain the I/O operation results. If the I/O request has been completed, the scheduling driver provides the I/O operation results to the application.