and Flow.lazyInit should be alligned (in their name and in their materialized values)
Gesendet: Montag, 05. März 2018 um 13:13 Uhr
Von: "Stefan Wachter"
An: akka-user@googlegroups.com
Betreff: [akka-user] Akka 2.5.11 - materialization of Flow.lazyInit
Hi,
studying the
Hi,
studying the newly Flow constructor Flow.lazyInit
def lazyInit[I, O, M](flowFactory: I ⇒ Future[Flow[I, O, M]], fallback: () ⇒ M): Flow[I, O, M]
(cf. https://doc.akka.io/api/akka/2.5.11/akka/stream/scaladsl/Flow$.html) I wondered how (citation from ScalaDoc)
The materialized v
Hi all,
I implemented an abstraction called CtxFlow[In, Out, Mat] on top of Akka
flows that passes through a ctx object transparently. CtxFlow has a
create[Ctx]() method that converts a CtxFlow[In, Out, Mat] into a
Flow[(In, Ctx), (Out, Ctx), Mat]. Most of the CtxFlow combinators can be
imple
> will complete never, if it completes eager elements in the feedback cycle
> get lost).
>
>
>
> I think that using some kind of poison pill could be used. However, is
> there some principled mechanism that might be used?
>
>
>
> Mit freundlichen Grüßen / Best reg
Hi all,
starting an application I see the following log output:
[AppClassLoader@1f17ae12] error can't determine implemented interfaces of
missing type
akka.stream.impl.VirtualProcessor$WrappedSubscription$$SubscriptionState
when processing declare parents
akka.stream.impl.VirtualProc
ala bug or something weird is going
> on in your system as there shouldn't be more than one instances of None.
>
> Can you cross-post your question on the Scala mailing list? They might be
> able to provide more help as my knowledge ends here unfortunately.
>
> -Endre
&g
sure you are not mixing incompatible Scala
versions or artifacts released for different versions of Scala?
>
>
> What JVM version are you using?
>
>
> -Endre
>
Am Mittwoch, 11. Mai 2016 09:08:39 UTC+2 schrieb Stefan Wachter:
>
> Hi all,
>
> after som
A Source[Attributes] implemented by a custom GraphStage might be the solution. Is there something easier?
Gesendet: Freitag, 04. März 2016 um 17:22 Uhr
Von: "Stefan Wachter"
An: "Akka User List"
Betreff: [akka-user] Usage of "nameLifted" in GraphDSL
Hi all,
Hi all,
I have some processing logic encoded in a flow F that is constructed using the GraphDSL (Scala version). The flow is included in a larger processing graph at multiple positions. Inside of F I need a unique identifier for every instantiation (i.e. materialization) because the various mat
Hi all,
I struggle for a while with implementing a multiplexer processing stage. An additional complication is, that the multiplexer processing stage should be built incrementally, i.e. the same multiplexer stage should be used at various points in the whole processing graph and at each point a
whole flow can not work properly any more.
Thanks again,
Stefan
Am Mittwoch, 25. November 2015 17:26:16 UTC+1 schrieb Akka Team:
>
> Hi Stefan,
>
> On Wed, Nov 25, 2015 at 5:17 PM, Stefan Wachter > wrote:
>
>> Hi Endre,
>>
>> now I watch for the de
Hi Endre,
now I watch for the death of the materialized actor for pushing notification. However, it takes more than 1 minute after the web socket is closed before a corresponding Terminated messages arrives. Is this an expected behaviour?
Cheers
Stefan
Gesendet: Mittwoch, 25. Novem
Hi Endre,
many thanks for the advice. After updating to 2.0.M1 it works nicely.
However, I struggle with two more issues:
1. How can I react on the event that the web socket is closed? Should I simply watch for the death of the actor whose ActorRef is registered with the UpdateActor?
Hi all,
I want to use a web socket connection
1. to push periodically results from the server to the browser
2. to send requests from the browser to the server and return the corresponding results to the browser (there might be many results, therefore the results should be streamed into th
14 matches
Mail list logo
