I've recently sat down to give Akka Http a try with the goal of using it to serve up a websocket where a client connects, and then receives push updates at some interval.
As I've been working through the ws examples in the manual all of them show a straight forward message-in/message-out workflow. Are there any patterns for when one wants to keep the client connected and continually send him push updates, or is that frowned upon given the reactive nature of the API? Should i be trying to construct an ActorPublisher in my message handler? Are there any examples out there? - Thanks in advance, Rich. -- >>>>>>>>>> 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.
