在应用程序（软件）中构建逻辑的极端可能是什么，即 GMail 附件验证
我最近访问了 GMail 博客，发现了软件内部逻辑构建的极点，
即
再也不会忘记附件
Gmail 会在您的电子邮件中查找短语 这表明您打算附加一个 文件（例如“我已附加”或 “参见附件”）并警告您如果 看起来你忘记这样做了。每一个 一天，这节省了很多人的时间 不得不发送的尴尬 实际上跟进电子邮件与文件 附后。
（来源：blogspot.com)
我认为这太多了...
请分享您对软件/应用程序内部逻辑构建的极端点的经验。
I have recently visted the GMail Blog, and found the extreme point of logic building inside software,
i.e.
Never forget an attachment again
Gmail looks for phrases in your email
that suggest you meant to attach a
file (things like "I've attached" or
"see attachment") and warns you if it
looks like you forgot to do so. Every
day, this saves tons of people the
embarrassment of having to send a
follow up email with the file actually
attached.
(source: blogspot.com)
I think this is too much...
Please share your expreience about the extreme point of logic building inside software/application.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Google 正在为他们的应用程序编写他们的代码。
如果上下文是一个用于发送邮件消息的公共库，那么您的“这太多了”的论点可能更有分量。在这种情况下，更好的方法可能是提供一个 hook ，代码可以在其中安装后可以检查文本和附件，并在某些内容看起来不正确时发出警告。
附加/未附加问题非常常见，这是 Google 在 Gmail 中处理该问题的完全合理的方式。最有可能的是，它位于检查空消息和空白主题行的同一代码块中。
Google is writing their code for their application.
If the context were instead a public library for sending mail messages, then your argument of "this is too much" might have more weight. In that case, a better approach might be to provide a hook where code can be installed that can check the text and attachments and issue a warning if something doesn't look right.
The attached / not attached issue is very common and this is a completely reasonable way for Google to handle it in Gmail. Most likely it is in the same block of code that checks for empty messages and blank subject lines.