The dcache has to be installed in all nodes that are willing to take the advantage of the content mesh. Once installed, the browser or any user agent should start using it's local dcache as a proxy. dcache can then find nodes with cached URLs with appropriate freshness and promote them from peer proxy status to parent proxy state on the fly and on a per request basis. The Figure 2 illustrates how dcache operates in a networked environment. dcache supports following HTTP features as well.
- Persistent connections
- HTTP pipe-lining
- HTTP tunneling
- Caching based on Expire, ETag, Last-Modified-Date, Cache-Control headers
We have tested this system on IEEE 802.11a/b/g networks in both infrastructure and ad-hoc mode and also in IEEE 802.11s mesh networks. Performance in those networks were fine and up to the expectations. Right now we are busy porting the system to Windows platform, in next couple of weeks we will hopefully complete the Windows port and the Admin UI driving the project towards it's first release.