Hi, I'm experimenting with Akka HTTP and reactive streams. Currently, I'm thinking about unreliable clients that have successfully established a (reverse) Akka HTTP stream chunking connection to some HTTP endpoint/server. In other words, the server response (to the client HTTP connection) is a chunk based producer (communicated via the HTTP response's HTTPEntity). In my specific example, I'm thinking about the producer being an ActorProducer instance.
If the client is restarted and the connection reestablished, then the server side (actor) producer will find itself in a situation whereby it thinks it has multiple subscribers. As a result, it looks like one should detect the connection closure (on the server side) and then cancel any existing (actor) producer subscription. So, is it possible to detect the connections closure? Or maybe my use-case could do with some refinement? Any help greatly appreciated, Carl. -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
