Abstract: A method, system and computer program product for preserving event data for lazily-loaded macro components. Upon detecting an event published by a publisher, the logical channel of the detected event is identified. If one of the macro components to be lazily-loaded is a primary receiver for that logical channel (determined by performing a table-lookup of a data structure containing a listing of macro components and their associated logical channels for which they are to be the primary receivers), then the indication of the logical channel of the detected event along with the data of the published event are stored as a key/value pair in a data structure. Upon the macro component to be lazily-loaded having been loaded, the data of the published event associated with the logical channel for which the loaded macro component is a primary receiver is retrieved and transmitted to that logical channel.

Abstract: An object request associated with a requesting entity can be identified. The object request can comprise of an object identifier and an object type associated with an object instance which can be a renderable entity. The entity can be a widget within an application executing within a client device. An object type associated with the object request can be determined which can be decomposed into an attribute request based a selected schema. The attribute request can comprise of an object instance identifier and an attribute identifier associated with an attribute value. An attribute index associated with a client-side object cache can be queried for the attribute value. When the attribute value exists in the attribute index, an appropriate attribute value associated with the attribute can be conveyed to the entity. When the attribute value is absent from the attribute index, the attribute request can be conveyed to a request aggregator.

Abstract: An object request associated with a requesting entity can be identified. The object request can comprise of an object identifier and an object type associated with an object instance which can be a renderable entity. The entity can be a widget within an application executing within a client device. An object type associated with the object request can be determined which can be decomposed into an attribute request based a selected schema. The attribute request can comprise of an object instance identifier and an attribute identifier associated with an attribute value. An attribute index associated with a client-side object cache can be queried for the attribute value. When the attribute value exists in the attribute index, an appropriate attribute value associated with the attribute can be conveyed to the entity. When the attribute value is absent from the attribute index, the attribute request can be conveyed to a request aggregator.

Abstract: A skill finder service receives directly from a user or through a social networking service a request for help with an asset. The skill finder service finds users skilled in the asset from asset data collected by an asset management service. The skill finder service searches the asset data for assets that match the asset in the request, and for each matching asset, determines the user who owns the matching asset. The skill finder service creates a list of skilled users and sends the list to the requesting user. The requesting user can contact one or more of the skilled users for help with the asset. The skill finder service uses existing data typically obtained by asset data management services to provide a valuable service to users. Further, by using the asset data to find skilled users, the skill finder service lessons or eliminates the need for user-entered expertise listing.

Abstract: A method, system and computer program product for updating the display state of the user interface of a subscriber client. A macro component definition file is inspected to obtain the listing of events associated with each macro component listed in the macro component definition file. An event callback function is created for each macro component listed in the macro component definition file, where the callback function will update the displayed user interface of the subscriber client to be the display state of the macro component when one its associated events is published by the publisher. Upon detecting a published event, the event callback function associated with the published event is executed thereby automatically updating the display state of the user interface of the subscriber client to be the display state of the macro component associated with the published event.

Abstract: A method, system and computer program product for preserving event data for lazily-loaded macro components. Upon detecting an event published by a publisher, the logical channel of the detected event is identified. If one of the macro components to be lazily-loaded is a primary receiver for that logical channel (determined by performing a table-lookup of a data structure containing a listing of macro components and their associated logical channels for which they are to be the primary receivers), then the indication of the logical channel of the detected event along with the data of the published event are stored as a key/value pair in a data structure. Upon the macro component to be lazily-loaded having been loaded, the data of the published event associated with the logical channel for which the loaded macro component is a primary receiver is retrieved and transmitted to that logical channel.

Abstract: An object request associated with a requesting entity can be identified. The object request can comprise of an object identifier and an object type associated with an object instance which can be a renderable entity. The entity can be a widget within an application executing within a client device. An object type associated with the object request can be determined which can be decomposed into an attribute request based a selected schema. The attribute request can comprise of an object instance identifier and an attribute identifier associated with an attribute value. An attribute index associated with a client-side object cache can be queried for the attribute value. When the attribute value exists in the attribute index, an appropriate attribute value associated with the attribute can be conveyed to the entity. When the attribute value is absent from the attribute index, the attribute request can be conveyed to a request aggregator.

Abstract: An object request associated with a requesting entity can be identified. The object request can comprise of an object identifier and an object type associated with an object instance which can be a renderable entity. The entity can be a widget within an application executing within a client device. An object type associated with the object request can be determined which can be decomposed into an attribute request based a selected schema. The attribute request can comprise of an object instance identifier and an attribute identifier associated with an attribute value. An attribute index associated with a client-side object cache can be queried for the attribute value. When the attribute value exists in the attribute index, an appropriate attribute value associated with the attribute can be conveyed to the entity. When the attribute value is absent from the attribute index, the attribute request can be conveyed to a request aggregator.

Abstract: A skill finder service receives directly from a user or through a social networking service a request for help with an asset. The skill finder service finds users skilled in the asset from asset data collected by an asset management service. The skill finder service searches the asset data for assets that match the asset in the request, and for each matching asset, determines the user who owns the matching asset. The skill finder service creates a list of skilled users and sends the list to the requesting user. The requesting user can contact one or more of the skilled users for help with the asset. The skill finder service uses existing data typically obtained by asset data management services to provide a valuable service to users. Further, by using the asset data to find skilled users, the skill finder service lessons or eliminates the need for user-entered expertise listing.