TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Designing Network Protocols

66 点作者 tomazmuraus大约 13 年前

5 条评论

trout大约 13 年前
As someone who troubleshoots networks for living, it can't be overstated what value easily understood information has. Normal factors such as lack of understanding of a system, miscommunication, false assumptions, false information, all types of bugs, and operator error already plague troubleshooting. Anything you can do to simplify is extremely important. Little things like being able to read debugs directly out of wireshark can make the difference between solving something between minutes and hours, days and weeks.<p>Unfortunately serviceability is not normally high in the initial product requirements, but I've seen a direct correlation between customer satisfaction in support and products/protocols/designs with good serviceability.
jacques_chester大约 13 年前
I think the short version is: in the past 5 years, simple wire-oriented serialisation formats have become much more common. At the time you had your pick of ASN (humongous) or Thrift (brand new).
评论 #3623916 未加载
评论 #3623781 未加载
评论 #3623813 未加载
alfiejohn_大约 13 年前
There's a complete chapter in The Art of Unx Programming about the importance of being textual:<p><pre><code> http://catb.org/~esr/writings/taoup/html/textualitychapter.html</code></pre>
tptacek大约 13 年前
HTTP-style query strings are a horrible format, whether you like ASCII or not.
alexchamberlain大约 13 年前
I would accept the ease of debugging argument if these messages weren't so small and so common. 1000 servers constructing strings and sending them over the network once a second is a nontrivial waste of resources.