Akka HTTP module in 2.0

[gutzeit]

Hi,

I was using the http module in the 1.x branch heavily and now starting designing a new part of the system with 2.0 I miss the "simplicity" for setting REST endpoints with the jetty-jersey bundle that were provided by akka-http and launched by microkernel.

I understand that it will be replaced by Play! so the questions is when ? Will it be "that easy" to implement endpoints as in 1.x ? When the documentation will be available ? Can I still use the old approach and make micokernel boot up Jetty like before ?

I read other http-module related topics but the last reply was from November last year, so I am testing the water again.

Thanks in advance.

[Jonas Bonér]

Have you tried Play Mini? https://github.com/typesafehub/play2-mini
What is missing there?

> --
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/akka-user/-/n5IVtHy0LXoJ.
> To post to this group, send email to akka...@googlegroups.com.
> To unsubscribe from this group, send email to
> akka-user+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/akka-user?hl=en.

--
Jonas Bonér
CTO
Typesafe - The software stack for applications that scale
Phone: +46 733 777 123
Twitter: @jboner

[Patrik Nordwall]

We also have this ticket http://www.assembla.com/spaces/akka/tickets/1538

Play2 master is now using akka 2.0-M4 but I think we need some stuff published to a public repo before it is useful. We are working on it.

Patrik Nordwall

Typesafe -  The software stack for applications that scale

Twitter: @patriknw

[gutzeit]

I have not but I am sure I can "mimic" the same functionality that 1.x had by play, jetty or any other web framework. What I miss is the simplicity :) Define http in the settings, launch microkernel and you are off.

[Jonas Bonér]

You are very welcome to contribute your ideas and code to make it even better.

> --
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/akka-user/-/Jkgc-SoTmNQJ.

[√iktor Ҡlang]

On Fri, Feb 10, 2012 at 10:46 AM, Jonas Bonér <jo...@jonasboner.com> wrote:
> On Fri, Feb 10, 2012 at 10:40 AM, gutzeit <gut...@gmail.com> wrote:
>> I have not but I am sure I can "mimic" the same functionality that 1.x had
>> by play, jetty or any other web framework. What I miss is the simplicity :)
>> Define http in the settings, launch microkernel and you are off.
>>
>
> You are very welcome to contribute your ideas and code to make it even better.

Yeah, I'm pretty sure it'd be quite simple to write your own
JettyExtension. Just take the Jetty-bootstrap code from 1.3 and write
a JettyExtension!

Cheers,
√

>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/akka-user/-/Jkgc-SoTmNQJ.
>>
>> To post to this group, send email to akka...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> akka-user+...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/akka-user?hl=en.
>
>
>
> --
> Jonas Bonér
> CTO
> Typesafe - The software stack for applications that scale
> Phone: +46 733 777 123
> Twitter: @jboner
>
> --
> You received this message because you are subscribed to the Google Groups "Akka User List" group.
> To post to this group, send email to akka...@googlegroups.com.
> To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
>

--
Viktor Klang

Akka Tech Lead

Typesafe - The software stack for applications that scale

Twitter: @viktorklang

[Henrik Engström]

Akka's Http documentation has been updated with how to use play-mini
in collaboration with Akka:
http://akka.io/docs/akka/snapshot/modules/http.html
HTH
//Henrik

2012/2/10 √iktor Ҡlang <viktor...@gmail.com>:

[phausel]

Hi Gutzeit,

Can you please elaborate on what you mean by simplicity? 

If you have an akka application, you would just need to add play-mini as a dependency, configure the main class for the HTTP server*, `sbt run` and your app is up and running.

(* https://github.com/typesafehub/play2-mini/blob/master/samples/scala/project/Build.scala#L12  

and https://github.com/typesafehub/play2-mini/blob/master/samples/java/project/Build.scala#L12 )

Thanks,

Peter

[Christer Sandberg]

Will Play mini contain more nice extractors like Unfiltered? Like Accepts to have different methods handling different content types etc.

/Christer

--
You received this message because you are subscribed to the Google Groups "Akka User List" group.

To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/5ybXigeJtPMJ.

[phausel]

Hi Christer, it certainly could. Please just file a ticket. Thanks Peter

[Jacobus Reyneke]

Hi,

It's a bit of a relieve to see that I'm not the only one having a bit of a hiccup in understanding the transition from Akka 1.x HTTP module to Play2-mini. I asked a related question on StackOverflow http://stackoverflow.com/questions/9586047/blending-akka-2-the-play2-mini-framework-and-http To date no-one answered though. Only received a helpful suggestion to consider Spray, but I would have loved to know exactly how Akka2 and Play2-mini was intended to work together if you have a requirement for both a HTTP Server and HTTP Client in the same solution.

Regards,

Jacobus

On Friday, 10 February 2012 11:50:25 UTC+2, Viktor Klang wrote:

On Fri, Feb 10, 2012 at 10:46 AM, Jonas Bonér  wrote:

> On Fri, Feb 10, 2012 at 10:40 AM, gutzeit  wrote:
>> I have not but I am sure I can "mimic" the same functionality that 1.x had
>> by play, jetty or any other web framework. What I miss is the simplicity :)
>> Define http in the settings, launch microkernel and you are off.
>>
>
> You are very welcome to contribute your ideas and code to make it even better.

Yeah, I'm pretty sure it'd be quite simple to write your own
JettyExtension. Just take the Jetty-bootstrap code from 1.3 and write
a JettyExtension!

Cheers,
√

>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/akka-user/-/Jkgc-SoTmNQJ.
>>
>> To post to this group, send email to akka...@googlegroups.com.
>> To unsubscribe from this group, send email to

>> akka-user+unsubscribe@googlegroups.com.

>> For more options, visit this group at
>> http://groups.google.com/group/akka-user?hl=en.
>
>
>
> --
> Jonas Bonér
> CTO
> Typesafe - The software stack for applications that scale
> Phone: +46 733 777 123
> Twitter: @jboner
>
> --
> You received this message because you are subscribed to the Google Groups "Akka User List" group.
> To post to this group, send email to akka...@googlegroups.com.

> To unsubscribe from this group, send email to akka-user+unsubscribe@googlegroups.com.

> For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.
>

[√iktor Ҡlang]

Hi,

I assume you've had a look at the Play-mini project site?

What in particular is missing?

Play-mini is based on Unfiltered, have you've read up on that?

Cheers,
V

To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/bn_Lhmcr0dUJ.

To post to this group, send email to akka...@googlegroups.com.

To unsubscribe from this group, send email to akka-user+...@googlegroups.com.

[Jacobus Reyneke]

Thanks Victor,

Yes I had a look at play-mini.

I did not mean to give the impression that something was missing from
play-mini, but I was just wondering how everything fits together. Play
was a web framework, and Akka a concurrency solution. Now they blended
a little and the responsibilities of the systems blended a little (it
appears that way to me in any case).

Let's take my current requirement as example:
I have a mobile app that needs to upload an image to a old-school web
service that uses SOAP. Now I'm considering using Finagle, or
Play-mini to accept the image as a base64 encoded message, wrap it in
a SOAP packet and pass it on to the existing web service.

What will Play-mini be responsible for and what will Akka be
responsible for. I'm looking at Play-mini as a mobile app supporting
web service solution, and Akka as a concurrency model that can
interact with the back end web service.

In short, what will a HTTP reverse proxy look like in Play-mini? Will
it still use some Akka HTTP functionality, or is it all the
responsibility of Play-mini.

The documentation and examples on Play-mini is still a little on the
thin side, so for a quick evaluation of the tool set, it's a little
hard to see how things fit together.

Regards,
Jacobus

>>> >> akka-user+...@googlegroups.com.
>>> >> For more options, visit this group at
>>> >> http://groups.google.com/group/akka-user?hl=en.
>>> >
>>> >
>>> >

>>> > --
>>> > Jonas Bonér
>>> > CTO
>>> > Typesafe - The software stack for applications that scale
>>> > Phone: +46 733 777 123
>>> > Twitter: @jboner
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups "Akka User List" group.
>>> > To post to this group, send email to akka...@googlegroups.com.
>>> > To unsubscribe from this group, send email to

>>> > akka-user+...@googlegroups.com.
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/akka-user?hl=en.
>>> >
>>>
>>> --
>>> Viktor Klang
>>>
>>> Akka Tech Lead
>>> Typesafe - The software stack for applications that scale
>>>
>>> Twitter: @viktorklang
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Akka User List" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/akka-user/-/bn_Lhmcr0dUJ.
>> To post to this group, send email to akka...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> akka-user+...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/akka-user?hl=en.
>

> --
> You received this message because you are subscribed to the Google Groups
> "Akka User List" group.
> To post to this group, send email to akka...@googlegroups.com.
> To unsubscribe from this group, send email to

[√iktor Ҡlang]

Hey Jacobus,

On Mon, Mar 12, 2012 at 2:53 PM, Jacobus Reyneke <jacobus...@gmail.com> wrote:

Thanks Victor,

Yes I had a look at play-mini.

Excellent

 

I did not mean to give the impression that something was missing from
play-mini, but I was just wondering how everything fits together. Play
was a web framework, and Akka a concurrency solution. Now they blended
a little and the responsibilities of the systems blended a little (it
appears that way to me in any case).

And at least in my world, they are very non-blended, as Akka does not depend on Play-mini, so nothing in Play-mini is blended into Akka.

 

Let's take my current requirement as example:
I have a mobile app that needs to upload an image to a old-school web
service that uses SOAP. Now I'm considering using Finagle, or
Play-mini to accept the image as a base64 encoded message, wrap it in
a SOAP packet and pass it on to the existing web service.

What will Play-mini be responsible for and what will Akka be
responsible for.

Play-mini is just a REST-layer, so essentially it maps from https requests back to http responses,

whatever goes in between is completely up to you.

 

I'm looking at Play-mini as a mobile app supporting
web service solution, and Akka as a concurrency model that can
interact with the back end web service.

 

In short, what will a HTTP reverse proxy look like in Play-mini? Will
it still use some Akka HTTP functionality,

There is no Akka HTTP functionality

 

or is it all the
responsibility of Play-mini.

I'd sy it's _your_ responsibility ;-)

 

The documentation and examples on Play-mini is still a little on the
thin side, so for a quick evaluation of the tool set, it's a little
hard to see how things fit together.

Did the docs for Unfiltered help clear some of it up? I'm very positive that Peter Hausel would love feedback on what can be improved in the docs.

Cheers,

√

[Ben Alexander]

I found this to be a really handy article:

http://letitcrash.com/post/17888436664/a-sample-application-showcasing-play-mini-and-akka

Regards,

Ben

[Jacobus Reyneke]

Hello again Victor,

Thanks for the informative and fun reply. I'll get my nose back into the docs. You gave me the direction I needed, and this time I'll approach it a little wiser. Thanks again.

Have a super day/night wherever you are. Here in Africa it's nap time ;-)

Cheers mate,
Jacobus

[Jacobus Reyneke]

Wow, thanks Ben!

Where was that article hiding when I searched for it? I owe you a beer ;-)

Have a good one,
Jacobus

--

You received this message because you are subscribed to the Google Groups "Akka User List" group.

To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/9gQT1QM-B40J.

[tigerfoot]

I second this sentiment!  There's just too much moving in one release here: a whole new understanding of the Actor ecosystem that replaces some foundational pieces of the model (e.g. Config, ActorRegistry, ...), then to lose the HTTP libraries and get directed to play-mini.  It's really a major hit.

Like others here I'm struggling to understand the play-mini integration but I have a lot of reading to do first.  I do need to understand if play-mini requires play2.  That would be horrible!  The beauty of the old Akka HTTP module was it was simple and tiny... just what I need for my featherweight cloud production environment.  I'm trying to avoid these heavy web frameworks like the plagues that they are.

Especially since the Akka docs say the 2.0 model will stick around for a while, I really wish they'd migrated the HTTP code to the 2.0 model first, then broken it off into a separate project or module if they didn't feel it fit with Akka proper.

If it turns out I need the Play2 framework to make all this work I'm screwed.

[Peter Vlugter]

You'll be happy to see that Yaroslav Klymko has ported akka-http to 2.0:

https://github.com/thenewmotion/akka-http

Announced recently on this thread:

https://groups.google.com/forum/#!topic/akka-user/AY0N2pLSSds

> --
> You received this message because you are subscribed to the Google Groups "Akka User List" group.

> To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/SztLFmZCRlsJ.

[√iktor Ҡlang]

Hi,

Everybody can choose for themselves the pace of which they want to progress, no one is forcing anyone to upgrade.

Typesafe offers the Typesafe Subscription that you can buy to get long term support packages.

Today there are many really good alternatives for doing REST with Akka,

Play! 2, Play-mini, Spray, Unfiltered etc, just pick which one suits your needs the most.

The reasons for dropping Mist has been outlined previously on this mailing list, search the archives for more background.

Cheers,

√

--

You received this message because you are subscribed to the Google Groups "Akka User List" group.

To view this discussion on the web visit https://groups.google.com/d/msg/akka-user/-/SztLFmZCRlsJ.

To post to this group, send email to akka...@googlegroups.com.
To unsubscribe from this group, send email to akka-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/akka-user?hl=en.

[Nick Kasvosve]

Hmm, I don't know. While what Victor says is true, surely the impact on existing user base must be considered when deprecating a major feature such as REST with Akka.

If an application depends on such a major feature, and then suddenly it gets dropped ...well, the client developers are left scrambling to find alternatives.

While again I understand that these things do happen, it just makes one apprehensive and wonder what other  module could be dropped next (or reworked to use some other technology).

Nick

[Jonas Boner]

On Tue, May 22, 2012 at 5:19 PM, Nick Kasvosve <nkas...@gmail.com> wrote:
> Hmm, I don't know. While what Victor says is true, surely the impact on
> existing user base must be considered when deprecating a major feature such
> as REST with Akka.

1. We dropped it for Akka 2.0. Which is such a big change to the 1.x
series that we could even give the project a new name. 2.0 is not in
any way backward compatible with 1.x - and our users love us for it.
Akka 2.x is SO MUCH better.
2. The former akka-http was a pretty bad module, lot's of problems,
short-comings, corner-cases. Just ask the Spray developers who based
first version of Spray on it, but then decided to write their own due
to all the problems.
3. I don't think an HTTP/REST module belongs as a core part of a
distributed computing/concurrency platform. It is better served as
add-on external modules.
4. When we created akka-http there was not any good alternatives out
there, but now there are so many: Play-Mini, Spray, Unfiltered, Socko,
Scalatra etc. Some listed here: http://akka.io/community/
5. No one forces you to upgrade. And if you are worried about the lack
of bug fixes in older versions - buy support for the Typesafe Stack -
that is one of the few things we do not give away for free, so support
us by buying support. Thanks.

I hope it makes more sense now.

/Jonas

--
Jonas Bonér
CTO

Typesafe - The software stack for applications that scale

[√iktor Ҡlang]

Hi Nick,

On Tue, May 22, 2012 at 5:19 PM, Nick Kasvosve <nkas...@gmail.com> wrote:

Hmm, I don't know. While what Victor says is true, surely the impact on existing user base must be considered when deprecating a major feature such as REST with Akka.

Of course! We have never changed anything without being able to motivate why. We don't go around changing this for the sake of changing things.

 

If an application depends on such a major feature, and then suddenly it gets dropped ...well, the client developers are left scrambling to find alternatives.

Of course not, alternatives were listed when the module was dropped, also, this is open source, so you can always port the module to the new version, or if you want support, that's always available through the Typesafe Subscription.

So the only one who is negatively impacted is one who wants to upgrade, doesn't want to switch to any of the, arguably superior, alternatives, doesn't want to put in any work of his own and doesn't want to pay for someone else to do it.

 

While again I understand that these things do happen, it just makes one apprehensive and wonder what other  module could be dropped next (or reworked to use some other technology).

This is equally solved by the previously stated solutions.

Cheers,

√

[tigerfoot]

Viktor,

Thanks for the tip on Spray! For myself and those who want a
lightweight HTTP capability w/o a heavy framework like Play, Spray is
going to fit the bill. Their latest 1.0-M2 supports Akka 2.0. It's
still a little rough and the docs are still, um, formative...but it
looks like a very well thought-out package. Just walking through the
Spray code I can see that Jonas is right: these guys have put an awful
lot of thought into how to handle HTTP in far more detail than the
Akka-HTTP package had.

After an evening of futzing around I got their "hello world" example
running stand-alone (outside sbt) on spray-server (HTTP server
abstraction) sitting on top of spray-can (their low-level tiny
server). I organized all the artifacts into a layout nearly identical
to Akka's microkernel.

I still have lots to learn and understand about Spray to get to a
point of being useful, but I'm happy. I've got Akka, HTTP, and Scala
all working together in a very tiny package...and I'm not stuck on the
older Akka architecture.
:-)

Greg

On May 22, 1:43 pm, √iktor Ҡlang <viktor.kl...@gmail.com> wrote:
> Hi Nick,
>

> On Tue, May 22, 2012 at 5:19 PM, Nick Kasvosve <nkasvo...@gmail.com> wrote:
> > Hmm, I don't know. While what Victor says is true, surely the impact on
> > existing user base must be considered when deprecating a major feature such
> > as REST with Akka.
>
> Of course! We have never changed anything without being able to motivate
> why. We don't go around changing this for the sake of changing things.
>
>
>
> > If an application depends on such a major feature, and then suddenly it
> > gets dropped ...well, the client developers are left scrambling to find
> > alternatives.
>
> Of course not, alternatives were listed when the module was dropped, also,
> this is open source, so you can always port the module to the new version,
> or if you want support, that's always available through the Typesafe
> Subscription.
>
> So the only one who is negatively impacted is one who wants to upgrade,
> doesn't want to switch to any of the, arguably superior, alternatives,
> doesn't want to put in any work of his own and doesn't want to pay for
> someone else to do it.
>
>
>
> > While again I understand that these things do happen, it just makes one
> > apprehensive and wonder what other  module could be dropped next (or
> > reworked to use some other technology).
>
> This is equally solved by the previously stated solutions.
>
> Cheers,
> √
>
>
>
>
>
>
>
>
>
>
>
> > Nick
>

> > On Tue, May 22, 2012 at 3:06 PM, √iktor Ҡlang <viktor.kl...@gmail.com>wrote:
>
> >> Hi,
>
> >> Everybody can choose for themselves the pace of which they want to
> >> progress, no one is forcing anyone to upgrade.
> >> Typesafe offers the Typesafe Subscription that you can buy to get long
> >> term support packages.
>
> >> Today there are many really good alternatives for doing REST with Akka,
> >> Play! 2, Play-mini, Spray, Unfiltered etc, just pick which one suits your
> >> needs the most.
>
> >> The reasons for dropping Mist has been outlined previously on this
> >> mailing list, search the archives for more background.
>
> >> Cheers,
> >> √
>

> >> Typesafe <http://www.typesafe.com/> - The software stack for

> >> applications that scale
>
> >> Twitter: @viktorklang
>
> >>  --
> >> You received this message because you are subscribed to the Google Groups
> >> "Akka User List" group.
> >> To post to this group, send email to akka...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> akka-user+...@googlegroups.com.
> >> For more options, visit this group at
> >>http://groups.google.com/group/akka-user?hl=en.
>
> >  --
> > You received this message because you are subscribed to the Google Groups
> > "Akka User List" group.
> > To post to this group, send email to akka...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > akka-user+...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/akka-user?hl=en.
>
> --
> Viktor Klang
>
> Akka Tech Lead

> Typesafe <http://www.typesafe.com/> - The software stack for applications
> that scale
>
> Twitter: @viktorklang

[Roland Kuhn]

On 23 maj 2012, at 06:04, tigerfoot <gzo...@gmail.com> wrote:

> Viktor,
>
> Thanks for the tip on Spray! For myself and those who want a
> lightweight HTTP capability w/o a heavy framework like Play, Spray is
> going to fit the bill. Their latest 1.0-M2 supports Akka 2.0. It's
> still a little rough and the docs are still, um, formative...but it
> looks like a very well thought-out package. Just walking through the
> Spray code I can see that Jonas is right: these guys have put an awful
> lot of thought into how to handle HTTP in far more detail than the
> Akka-HTTP package had.
>
> After an evening of futzing around I got their "hello world" example
> running stand-alone (outside sbt) on spray-server (HTTP server
> abstraction) sitting on top of spray-can (their low-level tiny
> server). I organized all the artifacts into a layout nearly identical
> to Akka's microkernel.
>
> I still have lots to learn and understand about Spray to get to a
> point of being useful, but I'm happy. I've got Akka, HTTP, and Scala
> all working together in a very tiny package...and I'm not stuck on the
> older Akka architecture.
> :-)
>

Great to hear, thanks for sharing!

Regards,

Roland Kuhn
Typesafe — The software stack for applications that scale
twitter: @rolandkuhn

[Jonas Bonér]

On Wed, May 23, 2012 at 6:04 AM, tigerfoot <gzo...@gmail.com> wrote:

Viktor,

Thanks for the tip on Spray!  For myself and those who want a
lightweight HTTP capability w/o a heavy framework like Play, Spray is
going to fit the bill.  Their latest 1.0-M2 supports Akka 2.0.  It's
still a little rough and the docs are still, um, formative...but it
looks like a very well thought-out package.  Just walking through the
Spray code I can see that Jonas is right: these guys have put an awful
lot of thought into how to handle HTTP in far more detail than the
Akka-HTTP package had.

After an evening of futzing around I got their "hello world" example
running stand-alone (outside sbt) on spray-server (HTTP server
abstraction) sitting on top of spray-can (their low-level tiny
server).  I organized all the artifacts into a layout nearly identical
to Akka's microkernel.

I still have lots to learn and understand about Spray to get to a
point of being useful, but I'm happy.  I've got Akka, HTTP, and Scala
all working together in a very tiny package...and I'm not stuck on the
older Akka architecture.
:-)

Great. Profit. 

--
Jonas Bonér
CTO
Typesafe - The software stack for applications that scale

[Yaroslav Klymko]

Hi,

I added a bit more documentation to help to migrate from old akka-mist. Check it out.

https://github.com/thenewmotion/akka-http#requestmethod