> If Google edge caching really is critical, then I'd rather see an architecture in which the AMP content is signed by the originating site, and the signature is looked up and validated client-side.
AMP's purpose is to deliver content at minimal bandwidth and latency. Requiring the client to side-channel to the originating server (that can be God-knows-where relative to the requesting client) defeats the purpose of creating a system for low-bandwidth users to quickly fetch and display content on mobile devices.
AMP's purpose is to deliver content at minimal bandwidth and latency. Requiring the client to side-channel to the originating server (that can be God-knows-where relative to the requesting client) defeats the purpose of creating a system for low-bandwidth users to quickly fetch and display content on mobile devices.