Spray，Akka

本文介绍了Spray，Akka-http和Play，这是新HTTP/REST项目的最佳选择的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我将使用Scala和Akka Actors开发新的HTTP/REST服务.

I'm going to develop new HTTP/REST services using Scala and Akka Actors.

我有使用Play的经验，但是我真的不需要完整的Web框架. 根据我的阅读，我认为Spray是合适的选择. 我的问题来自新的AKKA-HTTP之后的Spray的未来.

I have experience working with Play, but I don't really need a complete web Framework. From what I read, I think Spray is a suitable choice. My question come from the future of Spray after the new arrived AKKA-HTTP.

Spray项目是否将独立于Akka-HTTP项目发展，还是将两个项目合并为一个Akka-HTTTP?

Does the Spray project will grow independently from the Akka-HTTP project, or are the two project going to be merged into one Akka-HTTTP?

如果我开始使用Spray开发，这会有什么影响? 我还读到Play将集成AKKA-HTTP. 所以我终于想知道a是否不应该与Play搭配使用?

What is the impact of this if I start developing with Spray? Also I read that Play will integrate AKKA-HTTP. So I finally wonder if a should not go with Play?

感谢您的帮助.

推荐答案

Spray已准备就绪，但是开发团队(Mathias Doenitz)现在在Akka-http上为Typesafe工作.

Spray is production ready, but the development team (Mathias Doenitz) works for Typesafe on Akka-http now.

Akka-http的状态为开发预览" .有模糊的承诺会在几个月内"全面发布，但您无济于事.

The status of Akka-http is "development preview". There are vague promises of a full release "within a few months", but nothing you can take to the bank.

2015年7月29日

在1.0 RC4版本中，Akka-HTTP的状态现在为候选发布". 它的功能在很大程度上与Spray.io竞争，人们普遍期望Spray.io将失去其发展动力. 目前，我不再建议将Spray.io用于新项目.

The status of Akka-HTTP is now "release candidate" with version 1.0 RC4. Its functionality is largely competing with spray.io, and the common expectation is that spray.io will lose it's development momentum. At this time I would not recommend spray.io for new projects anymore.

来自Typesafe的Jonas Boner将Akka-http称为"Spray 2.0".因此，不要期望Spray的任何将来版本，并且在某个时候您将不得不进行切换.我在Scala Days上看到了Jonas的Akka-http演示文稿，由于将DSL大部分保持不变(即使库的基础实现会有所不同)，因此似乎很容易将Spray代码移植到Akka-http.

Jonas Boner from Typesafe has referred to Akka-http as "Spray 2.0". So don't expect any future versions of Spray and at some point you'll have to make the switch. I saw Jonas' Akka-http presentation at Scala Days and it looks like porting Spray code to Akka-http should be straight forward as the DSL is mostly unchanged (even though the underlying implementation of the library will be different).

要专门回答您的问题:Spray作为一个单独的项目完成，正在以Akka-http的名称导入Akka(不是合并，因为Akka之前没有任何等效项).如果您现在需要开始开发，请使用Spray，如果您有能力处理预览版中不可避免的错误，请使用Akka-http.您的Spray代码将永远不会停止工作，但在较小的错误修复之外也将不受任何支持.所有新功能都将添加到Akka-http中，因此，您无需更新到Spray 2.0，而是更新到Akka-http.

To answer your questions specifically: Spray is finished as a separate project, it is being imported into Akka under the name Akka-http (not a merge as Akka didn't have any equivalent before hand). If you need to start development now go with Spray, if you can afford to work with the inevitable bugs in a preview release go with Akka-http. Your Spray code will never stop working, but it won't be supported either outside of minor bug fixes. All new functionality will be added in Akka-http, so instead of updating to Spray 2.0 you update to Akka-http.