Hey yonatan, yes we are using that at the moment. I dug a bit in the actual Akka code and to my understanding for each HTTP Connection a .serverLayer is created => actually using it wired together with a ByteString source should work fine.
However it is still mainly inteded for a HTTP server => you have to be careful when it comes to error behaviour and closing of the connection for example - its a bidi flow, you should not use it to just convert bytestrings to requests, you have to deal with responses as well (you might hook up dummy code, ... but still a request wants a response) - if you create a bytestring source with a single HTTP request you should not complete the source before you got the response (see https://github.com/akka/akka/issues/19373 for details) - if your sink fails with an error the serverLayer currently recovers and sends back a HTTP error response (which might be undesireable depending on your use case) plus some of the behaviour changed between 1.0 and 2.0 all in all for us its still the easiest way to get a http interpreter hooked up to a bytestring stream but there are some struggels with the approach -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
