How does the split-browser architecture of Silk handles HTTPS?
Everything the EC2 backend does, like recompressing images, pre-rendering pages, resolving DNS records, etc, would require man-in-the-middle interception and decryption of TLS/SSL connections. Not good. I hope they leave HTTPS connections untouched.
That said, for plain HTTP traffic, if they can manage to significantly reduce page loading times, well done. I would prefer to see the fundamental problem resolved of course (lower latency on wireless networks), instead of relying on a complex back-end which will no doubt have issues of its own (availability, bugs, etc).
Everything the EC2 backend does, like recompressing images, pre-rendering pages, resolving DNS records, etc, would require man-in-the-middle interception and decryption of TLS/SSL connections. Not good. I hope they leave HTTPS connections untouched.
That said, for plain HTTP traffic, if they can manage to significantly reduce page loading times, well done. I would prefer to see the fundamental problem resolved of course (lower latency on wireless networks), instead of relying on a complex back-end which will no doubt have issues of its own (availability, bugs, etc).