[akka-user] Re: [akka-stream] How to get materialization result in partial flow

The problem with this solution is absence of actorRef during upstream complete. Any ideas how to get it? пятница, 16 октября 2015 г., 15:18:51 UTC+6 пользователь Alexey Romanchuk написал: > > Finally ended with > > ```scala > val managedMySource = FlowGraph.partial(MySource()) {

[akka-user] Re: [akka-stream] How to get materialization result in partial flow

5 г., 11:48:27 UTC+6 пользователь Alexey Romanchuk написал: > > Hey hAkkers! > > I need your advise in akka streams materialization question. > > I have custom protocol source `MySource` of type`Source[String, ActorRef]` > which accepts messages to control protocol via Act

[akka-user] [akka-stream] How to get materialization result in partial flow

Hey hAkkers! I need your advise in akka streams materialization question. I have custom protocol source `MySource` of type`Source[String, ActorRef]` which accepts messages to control protocol via ActorRef after materialization. Example of message is something like connect to server or change

Re: [akka-user] Akka Streams 1.0 release date?

Patrik, is it any fundamental problems in API right now? Do you plan to break backward compatibility before 1.0? вторник, 10 марта 2015 г., 16:18:35 UTC+6 пользователь Patrik Nordwall написал: We will release 1.0 as soon as possible, but not earlier. We will continue to release frequent

[akka-user] Re: Confusing problem whilst testing a PushPullStage implementation of a sliding window

Carl, I mean that problem is not in your code, neither in akka-stream code, but in incorrect publisher behavior. Publisher should not send messages to downstream more that downstream requested. If you are interested in manual publisher you should call expectRequest and then send not more that

[akka-user] Re: [akka-http] Routing dsl and streams integration

, 2015 at 7:21:52 PM UTC-8, Alexey Romanchuk wrote: Hello! As I understand from docs akka-http seamless integrates with akka-stream by passing flow to handleWith method. Also we have well known routing dsl from spray with all these nested directives. But I can not figure out how to use them

[akka-user] [akka-http] Routing dsl and streams integration

Hello! As I understand from docs akka-http seamless integrates with akka-stream by passing flow to handleWith method. Also we have well known routing dsl from spray with all these nested directives. But I can not figure out how to use them together. I want to have routing dsl together with

Re: [akka-user] [akka-stream] Prebuilt Source with simple synchronous API

faced https://github.com/akka/akka/issues/16762 and right now it is impossible to provide high level API to custom sources instead of prebuilt ones. воскресенье, 25 января 2015 г., 20:09:07 UTC+6 пользователь √ написал: Hi Alexey, On Sat, Jan 24, 2015 at 11:20 AM, Alexey Romanchuk alexey.r

[akka-user] Akka stream and akka cluster

Hey hakkers! Do you have any plans to implement clustered stream materializer to distribute stream parts in cluster? If yes do you have any estimations or ETA? Right now it is possible to manually distribute load using futures and map async, but clustered materializer will be really cool.

[akka-user] [akka-stream] Prebuilt Source with simple synchronous API

Hey hakkers, I wonder why there is not such prebuilt Source that provides API to externally emit message by simple method call. I am talking about something like this: //building and starting flow val flow = ??? val source = ExternalSource[String] source.via(flow).to(BlackholeSink).run

Re: [akka-user] [akka-stream] Junctions documentation and specs

, Roland 23 jan 2015 kl. 07:02 skrev Alexey Romanchuk alexey.r...@gmail.com javascript:: Hey! Also there is not straightforward how backpressure works with Broadcast. What if one of the outputs is busy and another one is requesting for for new elements? As far as I understand from

Re: [akka-user] [akka-stream] Decrease buffer size for some stages

It is exactly what I have tried to achieve! You guys did amazing work with all akka streams. Thanks! :) четверг, 22 января 2015 г., 14:43:52 UTC+6 пользователь drewhk написал: Hi Alexey, On Thu, Jan 22, 2015 at 4:15 AM, Alexey Romanchuk alexey.r...@gmail.com javascript: wrote: Hey! I

[akka-user] Re: [akka-stream] Junctions documentation and specs

to downstream only when all substreams demand for new element. Is it correct? I think we should add this to docs. Thanks! среда, 21 января 2015 г., 9:01:00 UTC+6 пользователь Alexey Romanchuk написал: Hi again, hakkers! I can not find any documentation about conditions when juntions becomes completed

[akka-user] [akka-stream] Decrease buffer size for some stages

Hey! I have a stream that process incoming messages, assemble big message pack and send it to other system via network. Incoming messages are relatively small and I use big buffers to improve throughput for all stages related to these small messages. At the very end of stream I have message

Re: [akka-user] [akka-stream] Stages unit testing

Hi, looks very interesting and very useful especially for stages testing. Thanks! On Tue, Jan 20, 2015 at 5:26 PM, Endre Varga endre.va...@typesafe.com wrote: Hi, On Mon, Jan 19, 2015 at 5:54 PM, Alexey Romanchuk alexey.romanc...@gmail.com wrote: Hey hakkers! I am currently updating

[akka-user] [akka-stream] Junctions documentation and specs

Hi again, hakkers! I can not find any documentation about conditions when juntions becomes completed and how junctions propagate errors. Something like Merge completes when all of his input completes. Also there is no such cases in unit tests. Am I miss something? Sure this information can be

[akka-user] [akka-stream] Stages unit testing

Hey hakkers! I am currently updating old application built on akka-streams 0.4 to 1.0-MX API. I used Transformers and now migrate it to PullPushStages. In general migration is pretty easy, but I can not figure out how should I rewrite unit test for custom stages? In 0.4 transformers had

[akka-user] [akka-stream] Delayed retry

Hey hakkers! I have a transformer step which perform some IO operations. Sure IO can fails and currently I have no way to perform non blocking retry of failed message. What about introduction new flow/duct combinator which allows to automatically perform n retries with some delay in case of

[akka-user] [akka-stream] immutable.Seq in Transformer

Hello hakkers! Why immutable.Seq used in Transformer#onNext signature? It forces nested classes to use immutable.Seq instead of general Seq. And then we unable to use simple Seq(1, 2, 3). I suggest to use scala.collection.Seq in method declaration. Thanks! -- Read the docs:

Re: [akka-user] [akka-stream] immutable.Seq in Transformer

got it. thanks! On Wednesday, June 11, 2014, √iktor Ҡlang viktor.kl...@gmail.com wrote: We always use immutable datastructures wherever possible to do so. use: immutable.Seq(1,2,3) On Wed, Jun 11, 2014 at 7:41 AM, Alexey Romanchuk alexey.romanc...@gmail.com javascript:_e(%7B%7D,'cvml

[akka-user] [akka-stream] ActorConsumer and FlowMaterializer

Hello hakkers! I have check ActorConsumer trait in 0.3-SNAPSHOT and 0.3 release and API looks strange for me. In then one hand we have FlowMaterializer that manage how flow will be materialized and in then another RequestStrategy from ActorConsumer. It looks like both of them are manage ways