为服务台分配实施 RSS 提要是一个坏主意吗？
在我提出问题之前，我想先声明一下，我对 RSS 提要知之甚少。我很久以前就尝试过使用 Google Reader，但我不认为 RSS 是我的菜。现在，进入问题。
我工作的公司使用基于网络的定制帮助台系统。我被要求在其中实现 RSS 提要。具体来说，我被要求为每个支持代理的票证创建一个 RSS 源。这样，每当将票证分配给使用 RSS 阅读器的支持代理时，他们就会收到通知。问题是我不知道 RSS 是否适合这样做。票证经常被重新分配。假设 John Doe 和 Jane Doe 都订阅了各自的 RSS 源，以便在分配给他们的票证时收到通知。一张票被分配给 John Doe。 30 分钟后，经理改变主意，将票重新分配给 Jane Doe。这在 John Doe 的 RSS 阅读器中看起来如何？有没有办法把它从他的饲料中删除或者什么？
非常感谢。
Before I ask my question, let me just say that I know very little about RSS feeds. I tried using Google Reader a long time ago, but I just don't think RSS is my thing. Now, onto the question.
The company I work for uses a custom web-based help desk system. I have been asked to implement RSS feeds into it. Specifically, I have been asked to create an RSS feed for each support agent's tickets. This way, support agents that use RSS readers can be notified whenever a ticket gets assigned to them. The thing is I don't know if this is something that RSS would be good for. Tickets get reassigned frequently. So let's say that John Doe and Jane Doe both subscribe to their respective RSS feeds to be notified whenever a ticket gets assigned to them. A ticket gets assigned to John Doe. 30 minutes later, the manager changes his mind and reassigns the ticket to Jane Doe. How would this look in John Doe's RSS reader? Would there be a way to remove it from his feed or what?
Thank you very much.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
听起来您正在尝试使用 RSS 作为通知系统。当你完全从这个角度来看它时，这并不是一个糟糕的主意。最坏的情况是，支持人员会收到新票证的通知，并在登录后惊喜地发现该票证已不存在。
如果您查看像 JIRA 这样的东西，它会使用电子邮件通知来通知人们票证已分配。如果工单被重新分配，它的分配对象和将要分配的对象都会收到有关更改的通知。人们可以选择“收听”工单，并会收到工单上发生的任何已完成工作、状态更改等通知。
您可能需要考虑做这样的事情。维护大量的 RSS 提要可能会变得相当麻烦。如果支持人员离开会发生什么？通过电子邮件，您可以简单地将电子邮件重定向给另一个人。
至于删除消息，我很确定一旦将其发送到客户端，它就永远存在。
It sounds like you are trying to use RSS as a notification system. When you do look at it completely from this perspective, it isn't a terrible idea. At worst, the support person would get notified of a new ticket and log in to be pleasantly surprised that the ticket is no longer there.
If you look at something like JIRA, it uses email notification to inform people that tickets have been assigned. If a ticket gets reassigned, the person it was assigned to and the person that it will be assigned to are both notified of the change. People have the option to "listen" to tickets and will get notified of any work done, status change, etc that happens on the ticket.
You might want to consider doing something like this. Maintaining lots and lots of RSS feeds might get quite cumbersome. What happens if a support person leaves? With email you could simply redirect the email to another person.
As far as deleting a message, I'm pretty sure that once it is sent to the client, it is there for good.
RSS 提要通常可供公众不受限制地使用（如果他们知道 URL）。您可以决定使用 .htaccess 并向客户端提供登录凭据。
刷新后，它在 John's Doe RSS 阅读器中看起来会很好。
RSS feeds are generally available to public without restrictions (if they know the URL). You may decide to use .htaccess and provide clients with login credentials.
It would look just fine in John's Doe RSS reader after he refreshes it.