Abstract: A server has a processor a memory connected to the processor. The memory stores instructions executed by the processor to maintain a recipe database including a genus characterization of an infusible material and species of infusible materials within the genus characterization. Each species of infusible material has an associated recipe specifying infusible material course treatments. Each infusible material course treatment includes at least one set of fluid agitation parameters, at least one wait interval, at least on set of liquid injection parameters and a release parameter.

Abstract: A server has a processor a memory connected to the processor. The memory stores instructions executed by the processor to maintain a recipe database including a genus characterization of an infusible material and species of infusible materials within the genus characterization. Each species of infusible material has an associated recipe specifying infusible material course treatments. Each infusible material course treatment includes at least one set of fluid agitation parameters, at least one wait interval, at least on set of liquid injection parameters and a release parameter.

Abstract: Creating service accounts involves receiving an account identifier entered by a user via a user interface to initiate registering a user device with a network account. One or more host names are determined based on a domain name portion of the account identifier. The one or more host names need not be preconfigured on the user device. Connections are attempted with each of the one or more host names. Each of the connection attempts uses one or more application protocols associated with a type of the network account. It is determined that at least one of the connection attempts results in a successful connection, and a user account is configured on the user device based on a host and protocol combination associated with the successful connection.

Abstract: Creating service accounts involves receiving an account identifier entered by a user via a user interface to initiate registering a user device with a network account. One or more host names are determined based on a domain name portion of the account identifier. The one or more host names need not be preconfigured on the user device. Connections are attempted with each of the one or more host names. Each of the connection attempts uses one or more application protocols associated with a type of the network account. It is determined that at least one of the connection attempts results in a successful connection, and a user account is configured on the user device based on a host and protocol combination associated with the successful connection.

Abstract: The present invention relates generally to electronic devices with corresponding device DNA and specifically to such electronic devices that share objects by reference to this device DNA. The present invention includes sharing objects among two or more electronic devices with differing object processing capabilities. In particular, a plurality of descriptions of each of the two or more electronic devices and object meta-data, which describes objects, is referenced when objects are exchanged by the two or more electronic devices. For example, if a given electronic device requests an object that it can not process, the object may be transcoded so that this electronic device can process the object. The transcoding is a function of the electronic device's description, the object's object meta-data, and the intended use of the object.