ADO.NET 数据服务
我不熟悉 ADO.NET 数据服务，但它看起来很有用。 我所需要的只是一份有关该技术的优点和缺点的列表。 然而，为了避免任何好的/坏的讨论，我重新表述这个问题：
您会告诉同事/经理这个 ADO.NET 技术很棒并且需要在我们站点的下一次更新中实现吗？
It should solve the following: we're developing a site which maintains about 50 different database tables. Every day, an automated process is extracting data from this all to generate an XML file which is sent to the end users. The end users will only contact the server in the morning to receive data but will never send any data back.
一些数据管理员负责使所有数据保持最新。 此时，这意味着他们会看到一个动态数据站点，可以在其中进行细微调整。 该网站仍在开发中，可能会在几年内完全重写。 然而，一些管理员开始明确表示，他们有时需要进行“大量”更新。 （嗯，也许只是改变大约 200 条记录。）他们并不真的想从站点中的某个来源逐条记录地输入所有这些数据。 他们有需要添加的数据列表，并且希望能够以自动化方式完成此操作。
出于这个目的，数据服务似乎很棒。 但同样，我对这项技术并不熟悉。 一位同事已经说过这样的话：“我听说过这件事，但我认为这在很多方面都是一个糟糕的故事。” 但当要求详细说明时，他只是拒绝了......（他现在可能正在谷歌搜索这个话题。）无论如何，我有一个非常怀疑的同事和一些经理说服他们这是有用的。 实际上，添加数据服务很容易，开发代码中已经有了。 （花了 45 分钟才让它工作。）现在，只要数据管理员需要添加更多数据列表，我就可以动态创建自定义客户端应用程序。 所以我在这里看到了一个很大的优势。 不过这还不够有说服力……
I'm not familiar with ADO.NET Data Services but it looks usable. All I need is a list of pro's and con's about this technique. However, to avoid any good/bad discussions, I'm rephrasing this question:
What would you tell a fellow coworker/manager that this ADO.NET technique is great and needs to be implemented with the next update from our site?
It should solve the following: we're developing a site which maintains about 50 different database tables. Every day, an automated process is extracting data from this all to generate an XML file which is sent to the end users. The end users will only contact the server in the morning to receive data but will never send any data back.
A few data administrators are responsible for keeping all the data up-to-date. At this moment, this means that they see a Dynamic Data Site where they can make minor adjustments. This site is still work-in-progress and will probably be completely rewritten in a few years.
However, some administrators start to make it clear that they sometimes need to do a "massive" amount of updates. (Well, maybe just altering about 200 records.) They don't really want to type all this data over from some source in the site, record by record. They have lists of data that need to be added and would prefer if this could be done in an automated way.
For this purpose, Data Services would appear to be great. But again, I'm not familiar with this technique. One co-worker already said something like: "I've heard about it and but I think it's a bad story in many ways." But when asked to elaborate, he just refused... (He's probably Googling about this topic right now.) Anyways, I have one very skeptical coworker and a few managers to convince them that it's useful. Actually, adding data services was easy and the development code already has them. (Took most of 45 minutes to get it working.) As it is now, I can create custom client applications on the fly whenever the data administrators need to add more lists of data. So I see a big advantage here. It's not convincing enough, though...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
看来，ADO.Net 数据服务可以允许客户端以您选择的格式实时使用数据，而不是离线导出客户端稍后下载的数据。
根据您的情况，这可能是一个很大的好处。
It appears that ADO.Net data services can allow clients to consume data in real-time, in your chosen format, as opposed to doing off-line exports of the data that the clients download later.
Depending on your scenario this can be a big benefit.