Stealth: Peer Service

[cookiengineer]

The Peer Service needs to be reimplemented after the Peerer Middleware has been implemented with all its features.

• [ ] Implement a way to download a beacon entry from a remote peer
• [ ] Implement a way to download a cache entry from a remote peer
• [ ] Implement a way to download a host entry from a remote peer
• [ ] Implement a way to download a policy entry from a remote peer
• [ ] Implement a way to download a redirect entry from a remote peer

Maybe above features can be solved with a synchronization approach that acts per-URL or per-domain?

Per Domain would probably be easier, because per-URL requires all HTML parsers and Asset-based APIs to work; otherwise there will be errors with downloaded media files, stylesheets and other linked content.