BREAKING: Typesafe acquires spray!

[Mathias Doenitz]

Everybody,

it is with our greatest pleasure that we are able to announce to you today the acquisition of spray by Typesafe!

Here is the press release: http://www.marketwired.com/press-release/Typesafe-Reactive-Platform-Acquires-New-High-Performance-HTTP-Foundation-1841738.htm
And here the post on the Typesafe blog: http://typesafe.com/blog/typesafe-gets-sprayed

tl;dr
After the 1.0/1.1/1.2 release spray will become an Akka module (akka-http) and the future HTTP stack underlying the Play framework.

Stand by for more information and updates on this awesome development...

Cheers,
Mathias

---
mat...@spray.io
http://spray.io

[Martijn Hoekstra]

Congratulations! Well done!

--
You received this message because you are subscribed to the Google Groups "spray-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spray-user+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Michael Pilquist]

Congratulations!

[Ramon Buckland]

Congratulations! good job.

Ramon Buckland

ra...@thebuckland.com

[Ryan LeCompte]

Awesome!!

[André Silva]

Great news! Congrats ;-)

[Henry Saputra]

Congrats!!

Awesome news

- Henry

[Roch Delsalle]

Congratulations !

[Caoilte O'Connor]

Awesome news!

[Mark Harrison]

Congratulations! 

[Scott Clasen]

This. Is. Awesome.

[Thomas Lockney]

This is fantastic news! Really, really looking forward to seeing this become part of the standard stack (it already is, as far as I'm concerned, really). 

On Wednesday, October 16, 2013 8:24:51 AM UTC-7, Mathias wrote:

[Thomas Lockney]

Now that this is done, any chance 1.2-20130710 (or a more recent build) can get promoted to at least milestone status? (seriously, this is driving some of my coworkers crazy -- and, yes, I know there's not a lot of rational reason for the concern about how it's labeled.) ;~)

On Wednesday, October 16, 2013 8:24:51 AM UTC-7, Mathias wrote:

[Odd Möller]

And there was much rejoicing!

//Odd

On Wednesday, October 16, 2013, Mathias Doenitz wrote:

[ppurang]

Congratulations!  

[Ivan Topolnjak]

Congratulations Mathias, Johannes and all contributors! You have done an amazing job with Spray and I hope this leads the project through a path where it can help a lot more people than it is doing now, keep rocking! I sincerely hope the best for you all, best regards.

[Ian Forsey]

Amazing!

[Timothy Perrett]

Congratulations guys, this is great, and is a credit to all the hard work put in over the past couple of years, really great.

Would you be able to provide some further insight into what will change with this news, and how it might affect spray APIs etc? For example, the blog post mentions java compatibility, and that clearly is not going to fly with the epic use of HLists and directive composition... It would be great to have some insight on this (if available!), and how it might affect all the folks on the mailing list who have a significant investment in the 1.0 APIs (as they are so close to being final)

Awesome work, congrats again

Cheers, Tim 

[Alex Ivanov]

Congratulations! You did a great job and this is the best reward, i think =)

But, on the other hand, i'm also concerned about the future of Spray and its API. How much it would be integrated into Play framework? Only on the level of HTTP implementation or in some other form? Would it be possible to use Spray without Play? Will you continue to develop Spray (mostly can/routing/client) further?

[Luis Ángel Vicente Sánchez]

Awesome news but I'm also a bit worried about the awesome routing dsl if you are going to provide a Java API.

Anyway... well done! I hope that you could tell as a bit more during the scala exchange.

[David Kowis]

On 10/16/2013 01:15 PM, Alex Ivanov wrote:
> Congratulations! You did a great job and this is the best reward, i think =)

Indeed! It is very exciting news!

>
> But, on the other hand, i'm also concerned about the future of Spray and
> its API. How much it would be integrated into Play framework? Only on
> the level of HTTP implementation or in some other form? Would it be
> possible to use Spray without Play? Will you continue to develop Spray
> (mostly can/routing/client) further?

Also of note, could twirl become a real thing separated from the Play
infrastructure? :)

--
David

[Age Mooij]

Finally! :)

Congratulations Mathias and Johannes!!!

Age

[Jan-Pieter van den Heuvel]

Congratulations guys!
Will all spray modules be integrated into akka (including spray-json)?

Kind regards,
Jan-Pieter

Op 16 okt. 2013 21:47 schreef "Age Mooij" <age....@gmail.com>:

[Carsten Saathoff]

Good news! Congrats!

[Markus Jais]

Hi Mathias,

absolutely fantastic news. Thanks for all your hard work on spray!

Markus

---

Von: Mathias Doenitz <mat...@spray.io>
An: "spray...@googlegroups.com" <spray...@googlegroups.com>
Gesendet: 17:24 Mittwoch, 16.Oktober 2013
Betreff: [spray-user] BREAKING: Typesafe acquires spray!

--
You received this message because you are subscribed to the Google Groups "spray-user" group.

To unsubscribe from this group and stop receiving emails from it, send an email to spray-user+unsub...@googlegroups.com.

[Mathias Doenitz]

Thanks a lot for all your very positive feedback!
It's great to see everyone be just about as excited about this news as we are ourselves.

I'll try to quickly address all the questions that have come up so far:

> Will all spray modules be integrated into akka (including spray-json)?

All modules from the main spray codebase will find their way into Akka in some way or another.
This is the initial plan (might change):

- Restructure all spray modules into three new Akka modules
- akka-http-core
- spray-http
- spray-can
- spray-servlet
- akka-http (the "main" module for building HTTP integration layers) — depends on akka-http-core
- spray-routing
- spray-client
- spray-httpx
- spray-caching
- Java API (to be written from scratch)
- akka-http-testkit
- spray-testkit

The fate of spray-json is undecided so far, but it certainly doesn't make sense to have both play-json and spray-json around.
I'm sure we'll find a way to come up with some kind of "best-of-breed" solution in the midterm.

> Also of note, could twirl become a real thing separated from the Play infrastructure? :)

Yes, twirl will live on and probably be officially supported.
The Play team is going to adopt it, watch this repository: https://github.com/playframework/twirl

> Would you be able to provide some further insight into what will change
> with this news, and how it might affect spray APIs etc? For example, the
> blog post mentions java compatibility, and that clearly is not going to fly
> with the epic use of HLists and directive composition... It would be great
> to have some insight on this (if available!), and how it might affect all
> the folks on the mailing list who have a significant investment in the 1.0
> APIs (as they are so close to being final)

With the move into Akka we will *add* a routing DSL for Java, which will be completely independent from the existing routing DSL for Scala.
We will *not* compromise the Scala DSL in any way to make it Java-compatible.
However, we might choose to improve the Scala APIs where we (as the joint Akka/spray team) think that it'll make sense. Still, any API changes will be carefully weighed off against the expected migration pains. Going forward you can expect akka-http to provide the same level of migration support that we have all come to get used to (and love) from Akka.

> i'm also concerned about the future of Spray and
> its API. How much it would be integrated into Play framework?
> Only on the level of HTTP implementation or in some other form?

The first step will be to add another spray-based HTTP "driver" underneath Play in addition to the existing Netty-based one.
As a Play user changing the HTTP stack implementation from Netty to spray should be completely transparent to you.
Play will sit on top of the future akka-http-core and not use spray's routing DSL (maybe this will change in some future Play version but certainly not in the Play 2.x series).

> Would it be possible to use Spray without Play?

Absolutely!
The new akka-http module will give you everything that spray offers currently, especially what is currently spray-can, spray-routing and spray-client.
The goal is to provide everything you need for building a REST API and/or consume REST services without any Play parts being required.

> Will you continue to develop Spray (mostly can/routing/client) further?

Yes, absolutely.
akka-http will be a first class akka module and receive the same kind of attention and love as all other core modules.

> Now that this is done, any chance 1.2-20130710 (or a more recent build) can
> get promoted to at least milestone status? (seriously, this is driving some
> of my coworkers crazy -- and, yes, I know there's not a lot of rational
> reason for the concern about how it's labeled.) ;~)

We have committed to releasing RC1 before the scala.io conference next week,
so expect something soon.

Cheers,
Mathias

---
mat...@spray.io
http://spray.io

[Yuji Kiriki]

Congratulations Mathias!!!!

On Wed, Oct 16, 2013 at 10:24 AM, Mathias Doenitz <mat...@spray.io> wrote:

Everybody,

it is with our greatest pleasure that we are able to announce to you today the acquisition of spray by Typesafe!

Here is the press release: http://www.marketwired.com/press-release/Typesafe-Reactive-Platform-Acquires-New-High-Performance-HTTP-Foundation-1841738.htm
And here the post on the Typesafe blog: http://typesafe.com/blog/typesafe-gets-sprayed

tl;dr
After the 1.0/1.1/1.2 release spray will become an Akka module (akka-http) and the future HTTP stack underlying the Play framework.

Stand by for more information and updates on this awesome development...

Cheers,
Mathias

---
mat...@spray.io
http://spray.io

--
You received this message because you are subscribed to the Google Groups "spray-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spray-user+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Yuji Kiriki Rodríguez
Seven4N
[Tel] 6551077 / [Cel] 300-6039698
Calle 31 # 13A - 51 Torre 1 Of. 101 Ed Panorama.
http://s4n.co

[Timothy Perrett]

Well, this is just splendid :-)

Sent from my iPhone

> You received this message because you are subscribed to a topic in the Google Groups "spray-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/spray-user/IEVLn2ixAMQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to spray-user+...@googlegroups.com.

[Danny Trieu]

Congratulation... well done...

[benoit heinrich]

Excellent news and congrats to all the team which contributed to spray... I've been using it since M6 and it's a great pleasure to see that it's finally going to be part of the typesafe stack.

Again, big congrats to all of you contributors and specially to Mathias and Johannes.

Keep the good work guys ;)

[Alex Ivanov]

And how about spray-routing api? It's implementation is heavily dependent on shapeless HList and i'm doubt that such a dependency will get into Akka. I remember that no so long ago on scala ML, Eugene Burmako opened a discussion about adding default HList implementation into standard scala library. On the other hand you've also mentioned that have some ideas on replacing HList with something different. 

[Bob]

Congrats!! This is a perfect union!

Bob

[Mathias Doenitz]

Alex,

we are aware of the "problem" with the shapeless dependency and are in ongoing discussions with all involved (spray-, akka- and scala-teams as well as Miles) to come up with the best solution. Whatever it'll end up being the routing DSL will not be compromised.

Cheers,
Mathias
---
mat...@spray.io
http://spray.io

[Timothy Perrett]

I'm not sure we can say the routing DSL won't be compromised, right? Any extension to the API typically involves hflatMap et al, so it would mean breaking changes for all but the most out of the box implementations? (As someone with a tonne of custom extensions, that is certainly concerning)

Do keep us posted and please involve the community during the process.

Cheers

Sent from my iPhone

> You received this message because you are subscribed to a topic in the Google Groups "spray-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/spray-user/IEVLn2ixAMQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to spray-user+...@googlegroups.com.

[Age Mooij]

+1

I have quite a few custom directives myself and I'm very happy with the customizability of the current directive infrastructure. I remember trying to write custom directives in the pre-HList Spray 0.9 days and this is so much more powerful!

Safe the HList! :)
Age

[Mathias Doenitz]

Gentlemen,

again: don't worry about the Scala-side routing DSL.
If there are changes coming they will make the DSL better, not worse.
However, the basic directive infrastructure is solid and hasn't been touched for quite some time. I currently don't see any reason for change there.
(Except maybe for the ability to reflect over the routing structure at runtime...)

We have come to love the power of HLists ourselves and will *not* give that up.
The only question is in what way we best pull in an HList dependency. Ideally shapeless would become an acceptable dependency, we'll see whether and how this can be done.

Cheers,
Mathias

---
mat...@spray.io
http://spray.io

[Age Mooij]

Thanks for the reassurance :)

Age

[Stjepan Buljat]

Congrats!!!

On Wednesday, October 16, 2013 5:24:51 PM UTC+2, Mathias wrote:

Everybody,

it is with our greatest pleasure that we are able to announce to you today the acquisition of spray by Typesafe!

Here is the press release: http://www.marketwired.com/press-release/Typesafe-Reactive-Platform-Acquires-New-High-Performance-HTTP-Foundation-1841738.htm
And here the post on the Typesafe blog: http://typesafe.com/blog/typesafe-gets-sprayed

tl;dr
After the 1.0/1.1/1.2 release spray will become an Akka module (akka-http) and the future HTTP stack underlying the Play framework.

Stand by for more information and updates on this awesome development...

[Carlos Dañel Ferreyra]

Congratulations! This is fantastic news!

Should we expect any package name changes or other refactoring as part of this transition to the Akka umbrella?

Also, what seems to be the current issues with shapeless and Akka?

Carlos

[Mathias Doenitz]

Carlos,

> Should we expect any package name changes or other refactoring as part of
> this transition to the Akka umbrella?

Yes, check out my reply from Oct. 17th (on this thread).

> Also, what seems to be the current issues with shapeless and Akka?

There is no issue per se, it's just that Akka has to be very careful about adding any kind of adding new dependencies (since it is part of the core stack).

Cheers,
Mathias

---
mat...@spray.io
http://spray.io