Abstract: Versions of a service not reachable by a set of service requestors that use the service are removed. Multiple, different versions of a service are stored, along with metadata associated with the multiple, different versions of the service. The metadata is examined to determine one or more of the multiple, different versions of the service that are not reachable by the set of service requestors that use the service. Those versions are deleted.

Abstract: Versions of a service not reachable by a set of service requestors that use the service are removed. Multiple, different versions of a service are stored, along with metadata associated with the multiple, different versions of the service. The metadata is examined to determine one or more of the multiple, different versions of the service that are not reachable by the set of service requestors that use the service. Those versions are deleted.

Abstract: Versions of a service not reachable by a set of service requestors that use the service are removed. Multiple, different versions of a service are stored, along with metadata associated with the multiple, different versions of the service. The metadata is examined to determine one or more of the multiple, different versions of the service that are not reachable by the set of service requestors that use the service. Those versions are deleted.

Abstract: Versions of a service not reachable by a set of service requestors that use the service are removed. Multiple, different versions of a service are stored, along with metadata associated with the multiple, different versions of the service. The metadata is examined to determine one or more of the multiple, different versions of the service that are not reachable by the set of service requestors that use the service. Those versions are deleted.

Abstract: Versions of a service not reachable by a set of service requestors that use the service are removed. Multiple, different versions of a service are stored, along with metadata associated with the multiple, different versions of the service. The metadata is examined to determine one or more of the multiple, different versions of the service that are not reachable by the set of service requestors that use the service. Those versions are deleted.

Abstract: A handheld client framework system provides a server proxy client that services client requests for network accessible information and determines the server that is most appropriate to supply the requested information and sends information request packets to that server across the Internet and/or intranet. Server responses to information requests are received by the server proxy client. The server proxy client separates the response information into the appropriate data components. Data components are sent to the appropriate client. Presentation and logic components are temporarily stored in a one-behind cache on the client. A client will continue to use the presentation and logic components already installed or in the one-behind cache to service the current user request. Any updates sent by the server proxy client and stored in the one-behind cache are retrieved by the client upon subsequent use by the user.

Abstract: A handheld client framework system provides a server proxy client that services client requests for network accessible information and determines the server that is most appropriate to supply the requested information and sends information request packets to that server across the Internet and/or intranet. Server responses to information requests are received by the server proxy client. The server proxy client separates the response information into the appropriate data components. Data components are sent to the appropriate client. Presentation and logic components are temporarily stored in a one-behind cache on the client. A client will continue to use the presentation and logic components already installed or in the one-behind cache to service the current user request. Any updates sent by the server proxy client and stored in the one-behind cache are retrieved by the client upon subsequent use by the user.

Abstract: An appropriate version of a service for use by a service requestor is selected based on metadata. A request for a service object provided by a service is received from a service requestor. Multiple, different versions of the service are determined, and metadata associated with the multiple, different versions of the service is examined to select a version of the service that is compatible with the service requestor. The requested service object is instantiated from the version of the service that is compatible with the service requester. The service requestor is enabled to access the instantiated service object.

Abstract: Versions of a service not reachable by a set of service requestors that use the service are removed. Multiple, different versions of a service are stored, along with metadata associated with the multiple, different versions of the service. The metadata is examined to determine one or more of the multiple, different versions of the service that are not reachable by the set of service requestors that use the service. Those versions are deleted.

Abstract: Services having associated metadata meeting particular criteria can be discovered. One or more services are stored. The services provide service objects to service requesters. Service requestors include compiled code and the service objects include compiled code that is linked to the compiled code of a service requester at runtime and that is executable by the compiled code of the service requestor. A metadata file is associated with each one of the services. A query message is received and includes a search query specifying particular criteria. At least some of the metadata files are searched to determine if one or more of the metadata files contain metadata that matches the particular criteria. When at least one of the metadata files contains metadata matching the particular criteria, the service associated with the metadata file is identified.

Abstract: A handheld client framework system provides a server proxy client that services client requests for network accessible information and determines the server that is most appropriate to supply the requested information and sends information request packets to that server across the Internet and/or intranet. Server responses to information requests are received by the server proxy client. The server proxy client separates the response information into the appropriate data components. Data components are sent to the appropriate client. Presentation and logic components are temporarily stored in a one-behind cache on the client. A client will continue to use the presentation and logic components already installed or in the one-behind cache to service the current user request. Any updates sent by the server proxy client and stored in the one-behind cache are retrieved by the client upon subsequent use by the user.

Abstract: An image generating apparatus used in the field of image processing such as Computer Graphics. The image generating apparatus comprises an input unit for setting data related to a shape of each polygon, an attribute-data-setting unit for setting physical-property attribute data of the polygons, a view-point-data setting unit for setting data related to a view point, a boundary-box-dividing unit for dividing a boundary box enclosing all the polygons into a set of voxels of equal-size with parameters for the boundary box and a linear conditional expression, a segment buffer for registering intersection data per segment for each light source consisting of a thread of a processor assigned for each segment on one polygon and a ray-intercepting polygon at the time of intensity computation per pixel, and an intensity computing unit for checking an intersection with the registered ray-intercepting polygon first when computing an adjacent pixel in the same segment.