Skip to content
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.

move to akka http #155

Open
bblfish opened this issue May 24, 2015 · 3 comments
Open

move to akka http #155

bblfish opened this issue May 24, 2015 · 3 comments

Comments

@bblfish
Copy link
Member

bblfish commented May 24, 2015

This required https and https session renegotiation.

@bblfish
Copy link
Member Author

bblfish commented May 24, 2015

The first thing to test is if WebID authentication can be implemented in that akka branch. That requires one to see if one can get the client certificate from normal code.

Is Play now based on this version of akka-http? That would allow mean one could test if one can get hold of the certificate inside of Play.

@antonkulaga
Copy link

Play team claims to use akka-http as an alternative experimental backend in play 2.4.x
But do we really need play at all? In my opinion play is too heavy and contains a lot of stuff that we do not really need. I also do not like play routers, I think akka-http ones are better and more flexible

@bblfish
Copy link
Member Author

bblfish commented May 24, 2015

Wether Play is needed or not is another issue I suppose. Still if they do have the latest akka http version, then one could in one go switch the current implementation over and see what problems are, and then do a slow migration. There may be advantages with Play that we will only realise when moving completely to akka. So in any case it is worth knowing how they fit together. ( One advantage of Play until recenlty is that I coud do WebID-TLS authentication, which I could not do with akka )

@bblfish bblfish added this to the Move to akka milestone Feb 12, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants