[akka-user] Re: Modeling simple TCP protocol that isn't always request/response in akka-stream

2015-07-15 Thread Chad Selph
Thanks for the examples. I ended up just using ActorSink/ActorSubscriber and using akka-stream exclusively for the TCP layer (actors for the rest), but I may go back to the stream approach if I want to integrate stream backpressure into the protocol's backpressure. On Tuesday, July 14, 2015 at

[akka-user] Re: Modeling simple TCP protocol that isn't always request/response in akka-stream

2015-07-14 Thread Chad Retz
I just had to do this and I found the AsyncStage which allows out-of-band messages to get added to the stream. It and the DetachedStage are not yet documented[0] but after reading enough other code and taking some guesses, I was able to get out-of-band messages into my IMAP server via an

[akka-user] Re: Modeling simple TCP protocol that isn't always request/response in akka-stream

2015-07-01 Thread Chad Selph
I tried something like this, where I had a PushPullStage that accepted a Source into its constructor. It seemed like the wrong approach, because it seemed like I was just reimplementing a common merge functionality. On Wednesday, July 1, 2015 at 3:58:49 AM UTC+3, Chad Retz wrote: Although I

[akka-user] Re: Modeling simple TCP protocol that isn't always request/response in akka-stream

2015-06-30 Thread Chad Retz
Although I have not done this yet, I would assume you can do this with a PushPullStage that pushes in onPull. How the state gets there to know when to push in onPull is probably an implementation detail. On Monday, June 29, 2015 at 5:15:53 AM UTC-5, Chad Selph wrote: I'm currently rewriting a