I am debating if I should go with compression of the Yahoo Search Results from my proxy following this post [Yahoo Developer Blog Entry]. I am trying to work out if it will be A) easy, B) worth it and C) Where to put it.
I could compress the results back to the client or compress the results to the proxy and then decompress the results to the client. Either way I will have to code for some fallback support, because some people who use my App might not have compression support in their browser and thus my proxy will have to detect that.Does anyone have any thoughts?
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.
I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.
I'm trialing a newsletter, you can subscribe below (thank you!)
