Im finding the idea of Akka Stream a very nice fit to the application im building. Im building a realtime decision system with the following functionality.
1. Make HTTPS POST request to get a *sessionToken* string 2. Start a keep-alive service to ping session server at 3h intervals 3. Use *sessionToken* as payload when in connection message when connecting to TCP socket to start receive *DataItems* 4. Create a stream pipeline from the socket connection as a function from *DataItem => Decision* 5. Handle session management faults and any faults in the pipeline What I have so far is an Actor hierarchy with an FSM SessionManagerActor which contains the *sessionToken *state, it gets it from a child actor wich does the actual getSessionRequest, when SessionManagerActor receives the *sessionToken* it spawns a keep-alive actor. The problem starts when I want to use the *TCP* flow from Akka stream to setup the stream. All the ways im trying to connect the sessionToken as input the the TCP stream seems like an ugly hack and I cant figure out how to do error handling if i for example need to update the session token. What would be the best solution for a problem like this and should i use Akka Stream for all parts, even keep-alive actor etc. Any input is highly appreciated since i feel if i only get and understanding of this part of the problem I will be able to solve the actual decision support part. -- >>>>>>>>>> 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.
