玩得怎么样！与 ZK Framework 不同的框架
我希望在学习曲线、可用性、效率和使用场景方面有所不同。我想创建带有 JSON、XML 响应的 Web 服务，并在 Android 上使用它以及在网站上使用它。
我ZK很好，但是玩！对我来说是全新的。
谢谢&问候， 安缦
I want the difference in terms of learning curve, usability, efficiency and situations in which they should be used. I want to create webservice with JSON,XML responses and use it from an Android as well as use it on web site.
I am good in ZK but play! is completely new for me.
Thanks & regards,
Aman
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Zk 和玩吧！确实是两个非常不同的东西。我认为两者之间的主要区别是：
我过去曾短暂使用过 ZK，我认为 Play!比 ZK 更容易掌握，尽管这是一个非常相对的判断。不过，这里的方法有很大的不同，如果您想要创建基于 JSON/XML 的 Web 服务，那么就开始吧！看起来比 ZK 更可取，因为：
Play! 的缺点具体取决于您的具体要求；但我想到的一个问题是构建与更传统和遗留服务（例如 EJB）高度集成的 Web 服务。自从玩！应用程序并不真正遵守任何常见的 Java EE 标准（即使它们可以在 Java EE 容器中运行），您最终可能会自己编写大量集成代码，而不是让容器为您完成这些工作。
Zk and Play! are really 2 very different things. The main differences between the 2 that I think of:
I've used ZK briefly in the past and in my opinion Play! is easier to pick up than ZK, even though that's a very relative judgement. There's a big difference in approach here though, and if you're looking to create a JSON/XML based web service then Play! seems much preferable over ZK because:
The disadvantages of Play! really depend on your specific requirements; but one issue that comes to mind is building web services that integrate heavily with more traditional and legacy services (such as EJB, for example). Since Play! applications don't really adhere to any of the common Java EE standards (even though they can run in a Java EE container), you might end up writing a lot of integration code yourself rather than having the container do it for you.