Abstract: An intra Web-page navigation history mechanism allows history points to be tracked even for state transitions within the same Web page. A Web page may be subjected to a number of different state changes as the Web application executes. Along the way, a number of the state changes may be tracked as history points. When a history point is created, associated state is also recorded. When the history point is again navigated to, a navigation event may be raised along with the associated state for the history point. Various components (whether on the server or client) may listen to that event and reconstruct their respective states by using selective portions of the reconstruction state.

Abstract: An intra Web-page navigation history mechanism allows history points to be tracked even for state transitions within the same Web page. A Web page may be subjected to a number of different state changes as the Web application executes. Along the way, a number of the state changes may be tracked as history points. When a history point is created, associated state is also recorded. When the history point is again navigated to, a navigation event may be raised along with the associated state for the history point. Various components (whether on the server or client) may listen to that event and reconstruct their respective states by using selective portions of the reconstruction state.

Abstract: An intra Web-page navigation history mechanism allows history points to be tracked even for state transitions within the same Web page. A Web page may be subjected to a number of different state changes as the Web application executes. Along the way, a number of the state changes may be tracked as history points. When a history point is created, associated state is also recorded. When the history point is again navigated to, a navigation event may be raised along with the associated state for the history point. Various components (whether on the server or client) may listen to that event and reconstruct their respective states by using selective portions of the reconstruction state.

Abstract: Accessing data through a social network. User input may be received at a node in a social network requesting access to data or requesting a search for data. The node includes data for an entity. In some embodiments, the entity controls the data at the node exclusive of centralized control of the social network. The node further comprises one or more references defining relationships to other nodes. The relationships are defined on an informational basis such that information in data at one node is related through a relationship to information in data at another node. Each of the other nodes includes other data about other entities. Embodiments may further include receiving data at the node from one or more of the other nodes based on one or more of the relationships. At the node, the data from the other nodes may be published.

Abstract: An intra Web-page navigation history mechanism allows history points to be tracked even for state transitions within the same Web page. A Web page may be subjected to a number of different state changes as the Web application executes. Along the way, a number of the state changes may be tracked as history points. When a history point is created, associated state is also recorded. When the history point is again navigated to, a navigation event may be raised along with the associated state for the history point. Various components (whether on the server or client) may listen to that event and reconstruct their respective states by using selective portions of the reconstruction state.

Abstract: Facilitation of web page rendering using dynamic rendering controls. A server identifies a representation of a page to be downloaded to a client. The representation includes a dynamic rendering control that may be used to render a portion of the page. Rather than leaving it to the client to gain access to the initial set of data that is to be used by the dynamic rendering control to properly render, the server estimates the initial set of data that is to be used, and transmits a network response that includes the estimated initial set of data. When executing the rendering component, the client may simply use the data provided in the network response to render the portion of the page, rather than having to gain access to the data from a network source.