Skip to main content

7 posts tagged with "network"

View All Tags

⚡️ [Performance] How the browser optimizes resource downloads with HTML Preload Scanner

· 8 min read
卤代烃
微信公众号@卤代烃实验室

html-preload-scanner-hero-image.jpg

Hello everyone, I am skychx, specializing in performance optimization.

When doing web-related performance optimization, it is necessary to have a certain understanding of the underlying principles of the browser, so that the page can better walk on the happy path. Today, let's understand a browser default performance optimization scheme that is rarely known by people - HTML Preload Scanner, and see how it optimizes the loading speed of network resources.

⚡️ [Performance] Three ways to observe network performance data in the browser.

· 7 min read
卤代烃
微信公众号@卤代烃实验室

observe-browser-network-hero-image.jpg

Introduction

There are various ways to observe network performance data with the browser's Devtools tool, but these data are presented in different ways. This article is to interpret these performance data presentation methods and make a longitudinal comparison to help more people optimize the performance problems brought by the network.

🪢 [Network Protocol] A Brief Discussion on the Evolution of HTTP Priority Algorithms

· 8 min read
卤代烃
微信公众号@卤代烃实验室

http_%20prioritization_hero_img.jpg

A couple of days ago on "Jike," I spontaneously wrote a brief history of HTTP priority development. I felt it was too rushed at the time, so I decided to write a blog to expand on it, analyzing the concept of "priority" longitudinally to see the development and evolution of these fundamental protocols.


🍶 为什么你的 Charles 会抓包失败?

· 24 min read
卤代烃
微信公众号@卤代烃实验室

charles_hero_image.jpg

更新提示

文章已于 2022-08-22 更新

作为一名 Web 开发工程师,天天都会和网络打交道。Charles 作为一款网络抓包工具,几乎成了 Web 开发的标配。

本文是我深度使用 Charles 后总结而成,不同于其它介绍 Charles 的文章,这篇文章不会详细介绍 Charles 的各个功能(例如 remote 和 rewrite),而是专注于分析一个问题:什么情况下 Charles 会抓包失败?

🙈 How to Hide Your Hot Update Bundle Files?

· 15 min read
卤代烃
微信公众号@卤代烃实验室

A while ago, a senior person at our company learned through some channels that a certain national-level APP was rejected for three months because Apple App Store reviewers detected React Native hot update content. Our hot update platform has similar principles to the problematic APP, so we also face the risk of rejection. Therefore, we need to think of some ways to hide the hot update bundle and avoid being discovered by reviewers.

Actually, this problem is quite complex because it's not purely a technical issue but also involves various complex commercial interests. Under many constraints, it's difficult to find an optimal solution. Moreover, this issue is quite sensitive, so I can only briefly outline my thinking process. This article will not provide specific code implementations.

Serious declaration: If anyone hides hot update data according to the ideas in this article and the application gets rejected or removed, I will not be responsible.

🌐 Hidden Pitfalls in HTTP Specifications

· 11 min read
卤代烃
微信公众号@卤代烃实验室

The HTTP protocol is arguably the most familiar network protocol for developers. Its characteristics of being "simple and easy to understand" and "easy to extend" have made it the most widely used application-layer protocol.

Despite its many advantages, the protocol specification contains numerous hidden pitfalls due to various compromises and limitations during its definition, which can easily trap unsuspecting developers. This article summarizes common pitfalls in HTTP specifications to help developers consciously avoid them and improve their development experience.