Abstract: A cache server (18) may prefetch one or more web pages (30) from an origin server (16) prior to those web pages being requested by a user (13). The cache server determines which web pages to prefetch based on a graph (42) associated with a prefetch module (40) associated with the cache server. The graph represents all or a portion of the web pages at the origin server using one or more nodes (130) and one or more links (100) connecting the nodes. Each link has an associated transaction weight (102) and user weight (104). The transaction weight represents the importance of the link and associated web page to the origin server and may be used to control the prefetching of web pages by the cache server. The user weight may be used to change a priority (46) associated with a request (22) for a web page. The user weight and transaction weight may change based on criteria (50) associated with the origin server.

Abstract: A cache module (26) at a client computer (12) controls a cache portion (28) on a storage device (24). The cache module communicates with other cache modules at other clients to form a cache community (15). The cache modules store World Wide Web or other content in the cache portions for retrieval in response to requests (32) for content from browsers (30) in the cache community. When the requested content is not available in the cache community, the requested content may be retrieved from an origin server (19) using the Internet.

Abstract: A method and system for dynamic distributed data caching is presented. The method includes providing a cache community (402) comprising at least one peer (413). Each peer has an associated first content portion (511) indicating content to be cached by the respective peer. A client (404) may be allowed to join the cache community. A peer list (426) associated with the cache community is updated to include the client. The peer list indicates the peers in the cache community. A respective second content portion (511) is associated with each peer based on the addition of the client.

Abstract: A cache server (18) may prefetch one or more web pages (30) from an origin server (16) prior to those web pages being requested by a user (13). The cache server determines which web pages to prefetch based on a graph (42) associated with a prefetch module (40) associated with the cache server. The graph represents all or a portion of the web pages at the origin server using one or more nodes (130) and one or more links (100) connecting the nodes. Each link has an associated transaction weight (102) and user weight (104). The transaction weight represents the importance of the link and associated web page to the origin server and may be used to control the prefetching of web pages by the cache server. The user weight may be used to change a priority (46) associated with a request (22) for a web page. The user weight and transaction weight may change based on criteria (50) associated with the origin server.