Geographic Hash Table (GHT) scheme for data-centric storage is presented in [7]. A node hashes data to a unique location by data type, and routes the data to that location by a combined greedy face routing protocol. The nodes that enclose the harsh location in a planar graph store the data; the other nodes may get the data from any of these nodes. The main drawback of this scheme is the undesired non locality-aware data query, which means that a node near the data source may have to travel a long distance to retrieve the data. Also, it may induce bottleneck spots when some types of data are frequently generated or requested. Geography based Content Location Protocol (GCLP) utilizes content servers, which advertise their locations in four directions on a periodical basis [8]. Nodes receiving location advertisements become content location servers. ‘‘If a content location server receives multiple advertisements for a particular resource, it will only forward updates from the content server closest to it.’’ This forwarding policy is an informal definition of the blocking rule generalized, formalized and used for information mesh construction in [2]. Due to its periodic location advertisement, GCLP generates large message overhead.