如果我想在 IIS 中执行 REST，我现在应该使用 WCF Web Api 吗？
我需要创建一个在 IIS 上运行的 REST API，并与 WCF Web Api 一起使用。与普通 WCF 或现已弃用的 WCF 入门工具包相比，它似乎能够完成我想做的一切。我还没有真正尝试过这些，但 conneg 似乎很难或不可能，这是一个大问题，因为 conneg 是 HTTP 的许多很好的正交设计功能之一，因此，REST-on-HTTP，我打算完全利用我的优势。
问题：由于目前只有“预览版 4”版本（2011 年 4 月），我找不到太多关于微软预计何时发布它的信息（除了印象是今年或明年） - 我应该已经使用它了吗？
特别是当源代码在那里并且我可以（最坏的情况）自己进去修改和构建它时，使用经过充分测试的预览版本进行生产几乎感觉很安全。
更多细节：我想在本周开始创建原型，REST API 将在几个月内（今年）出现在生产机器上。我预计 API 仍会发生一些变化，并检查 活动 在 codeplex 上，它似乎正在积极开发中，但是我可以在这些更改的同时更改我的代码。
I need to create a REST API that runs on IIS and played with WCF Web Api. It seems to be able to do everything I want, in contrast to plain WCF or the now deprecated WCF starter kit. I haven't really tried those, but conneg seems to be hard or impossible, and that's a deal breaker, as conneg is one of the many nice orthogonally designed features of HTTP and hence, REST-on-HTTP, that I intend to fully use to my advantage.
Question: As currently there is only a "Preview 4" version out (April 2011), and I could not find much on when MS expects to release it (except an impression it will be either this year or next year) - Should I use it already?
Especially as the source code is there and I could - worst case - go in and modify and build that myself, it almost feels safe to go production with a - well-tested - preview build.
Some more details: I want to start creating prototypes this week and the REST API will end up on production machines in a matter of a few months (this year). I expect the API to still change a little bit, and checking the activity on codeplex it seems to be under active development, but I'm fine with changing my code alongside those changes.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Web Api 正在积极开发中，我们很快就会发布 Preview 5。事实上，如果您前往 codeplex，您会看到最近的一些提交来证明我的说法。
至于我们何时发布，目前还不能确定。然而，我们正致力于发布，并且由于我们正在发布与框架类似的带外版本，这给了我们更大的灵活性。
在下周的 Build 大会上，您将听到更多有关 Web API/我们的路线图的公告。
至于创建原型，这样做是没有问题的。我们有几个客户在内部和外部都依赖于 Web api 位。只要您了解这些位正在开发中/将会发生变化，并且不保证对每个 drop 的支持（通过 Codeplex 除外），您就可以自由使用这些位。明智的一项限制许可是，在开发过程中，您无法将它们部署在公司外部。
谢谢
格伦
Web Api is in active development, and we are revving for a Preview 5 release shortly. As a matter of fact if you head over to codeplex you will see several recent commits to prove my statement.
In terms of when we will release, we can't say that at this point. However we are on a committed train to release and as we are releasing out-of-band similar to the framework, that gives us much more flexibility.
At Build next week, you'll hear more announcements about web api / our roadmap.
As to creating prototypes, there is no problem in doing that. We have several customers that are depending on the web api bits both internally and externally. As long as you understand that the bits are in development / will change, and that there is no guaranteed support on each drop (other than through codeplex) you are free to use the bits. The one restriction license wise is you cannot deploy them outside your company while they are in development.
Thanks
Glenn
已经发布的（非 WCF）替代品（例如 OpenRasta）怎么样？
How about (non-WCF) alternatives that have already been released like OpenRasta?