软件更新通知

发布于 2024-07-29 07:11:07 字数 705 浏览 2 评论 0原文

我正在考虑为我网络应用程序之一实施某种软件更新通知< a href="http://www.devio.at/index.php/dbscript" rel="nofollow noreferrer">正在开发。

我遇到了几个问题:

  • 更新检查应该在客户端执行还是在服务器上执行?

客户端意味着,软件检索最新版本信息,执行检查并显示更新信息。

服务器端检查是指软件将版本信息发送到服务器,服务器进行计算并将信息返回给客户端。

我的猜测是,服务器端实现可能比客户端更灵活、更强大,因为只要客户端理解,我就可以轻松地向服务器添加功能。

  • 更新信息应该显示在哪里?

是否可以在登录屏幕上显示? 应该只有管理员才能看到吗? (这是一个带有数据库的网络应用程序,因此更新需要操作数据库网络,这只能由管理员完成)。 一个小小的蜂鸣闪烁图标怎么样,随着版本每天变得越来越过时,该图标的大小也会增加;)?

  • 隐私问题

并不是每个人都喜欢通过互联网广播他们的应用程序使用统计数据。

TheOnion 问题:怎么想?

I am considering implementing some sort of Software Update Notification for one of the web applications I am developing.

There are several questions I came across:

  • Should the update check be executed on the client or on the server?

Client-side means, the software retrieves the most current version information, performs its checks, and displays the update information.

Server-side check means the software sends its version info to the server, which in turn does the calculations and returns information to the client.

My guess is that server-side implementation may turn out to be more flexible and more powerful than client-side, as I can add functionality to the server easily, as long as the client understands it.

  • Where should the update info be displayed?

Is it ok to display on the login screen? Should only admins see it? (this is a web app with a database, so updating requires manipulation of db and web, which is only done by admins). What about a little beeping flashing icon which increases in size as the version gets more obsolete every day ;) ?

  • Privacy issues

Not everybody likes to have their app usage stats broadcast over the internet.

TheOnion question: What do you think?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

唠甜嗑 2024-08-05 07:11:07

这就是我的做法:

  • 更新过程在低优先级后台线程上运行。 它绝对不可能干扰程序的运行。
  • 客户端发送当前版本和当前区域性(区域设置)
  • 服务器回复版本号、向用户显示的本地化显示文本以及安装程序和版本页面的当前 URL(显示版本说明/更改列表)。 它实际上发送了 3 组 - 稳定版本、测试版本和夜间构建版本。
  • 我使用非模式对话框向用户提供立即安装、访问网站或取消的选项。 您还可以像 WinSCP 一样操作,并将更新通知放在系统托盘中。 另一种选择是在有更新可用时通过电子邮件将结果发送给用户。

当客户端运行非常旧的版本时,我会给出不同的更新消息,因为产品已重命名。

这是我的做法的图片。 它不是世界上最伟大的,但它一直在为我们完成工作,我们没有听到用户的任何抱怨。
nFringe 更新程序
(来源:280z28.org

Here's what mine does:

  • The update process runs on a low priority background thread. There's absolutely no way for it to ever interfere with the operation of the program.
  • Client sends the current version and the current culture (locale)
  • Server replies with a version number, localized display text to show the user, and the current URLs of the installer and the releases page (showing release notes/change list). There are actually 3 sets of these it sends - the stable version, beta version, and nightly build version.
  • I use a non-modal dialog to present the user with the option to install now, visit the website, or cancel. You could also operate like WinSCP and place your update notification in the system tray. Yet another option is emailing the results to the user when an update is available.

I give a different update message when the client is running a very old version because the product was renamed.

Here's a picture of the way I'm doing it. It's not the greatest in the world, but it's been getting the job done for us and we haven't heard any complaints from the users.
nFringe Updater
(source: 280z28.org)

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文