[
https://issues.apache.org/jira/browse/PIO-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644518#comment-16644518
]
ASF GitHub Bot commented on PIO-31:
-----------------------------------
dszeto commented on issue #474: [PIO-31] Move from spray to akka-http
URL: https://github.com/apache/predictionio/pull/474#issuecomment-428455520
I used to think that way as well, but I humbly disagree now. After I learned
about defense in depth
(https://reinout.vanrees.org/weblog/2017/05/02/https-behind-proxy.html is a
good read) and security audit, it is in fact a desirable feature. I can take on
that as a separate PR.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Move from spray to akka-http in servers
> ---------------------------------------
>
> Key: PIO-31
> URL: https://issues.apache.org/jira/browse/PIO-31
> Project: PredictionIO
> Issue Type: Improvement
> Components: Core
> Reporter: Marcin Ziemiński
> Assignee: Naoki Takezoe
> Priority: Major
> Labels: gsoc2017, newbie
>
> On account of the death of spray for http and it being reborn as akka-http we
> should update EventServer and Dashbord. It should be fairly simple, as
> described in the following guide:
> http://doc.akka.io/docs/akka/2.4/scala/http/migration-from-spray.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
