Hi all, what is the recommended (correct?) way to ensure a certain response timeout when using superPool flow? I think flow.completionTimeout (and friends) are not apropriate because they affect the whole flow of requests to responses whereas only a single request-response pair might have been affected by the timeout.
Studying the configuration options there seem to be only two settings that might be useful: connecting-timeout and idle-timeout. The first setting however does not track responses and the second setting is only indirectly linked with the original problem of having timeouts for responses. Can anyone advice? (PS: One could use nested flows of single requests to single responses and flatten / recover them or use the "Future-Based" variant of the API instead. Yet, I wonder if there is an easier solution.) Mit freundlichen Grüßen / Best regards Dr. Stefan Wachter Bosch Software Innovations GmbH Communications (INST-ICM/BSV-BS) Stuttgarterstr. 130 71332 Waiblingen GERMANY www.bosch-si.de www.blog.bosch-si.com<http://www.blog.bosch-si.com/> Tel. +49 711 811 58 477 Fax +49 711 811 58 100 external.stefan.wach...@bosch-si.com<mailto:daniel.mau...@bosch-si.com> -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
