As you expected I want to aggregate the elements of a stream. Perhaps
creation a second subscriber on the source (as you suggest) could be a
solution. I do not know what you mean by 'creation a second subscriber'
//Variance
//Calculate the variance from a source of integers with a reusable flow
Is Requester offering any benefits over ask in combination with pipeTo?
Thanks
Heiko
--
Heiko Seeberger
Home: heikoseeberger.de http://heikoseeberger.de/
Twitter: @hseeberger https://twitter.com/hseeberger
Public key: keybase.io/hseeberger https://keybase.io/hseeberger
On 29 Jul 2015, at
The subject pretty much says it all. I have the following in my pom:
!-- akka --
dependency
groupIdcom.typesafe.akka/groupId
artifactIdakka-actor_${scala.binary.version}/artifactId
version2.3.9/version
/dependency
dependency
groupIdcom.typesafe.akka/groupId
Brilliant, thank you!
On Wednesday, July 29, 2015 at 1:52:08 PM UTC-7, sfos...@twilio.com wrote:
The subject pretty much says it all. I have the following in my pom:
!-- akka --
dependency
groupIdcom.typesafe.akka/groupId
artifactIdakka-actor_${scala.binary.version}/artifactId
Seems you're mixing up dependencies.
Please don't use 2.3.9, use 2.3.12 (see your akka-actor dependency).
--
Cheers,
Konrad 'ktoso’ Malawski
Akka @ Typesafe
On 29 July 2015 at 22:52:05, sfosb...@twilio.com (sfosb...@twilio.com) wrote:
The subject pretty much says it all. I have the following
Hey Endre,
Thanks so much for doing this. I've looked through it (and skimmed the
new doc page) but haven't digested it well enough to say anything other
than thanks. :) I'll get back to you in the next day or so, perhaps
with a couple of questions.
Akka Team wrote:
And now I added
I now updated the gist with the reverse direction: Now a client sends a
String command and expects an Iterable[Int] back as a response. I currently
limited the funcionality to one request per connection, since otherwise I
would need a bit more elaborate codec which would complicate the example (I
Hi Derek,
It is not that hard, but you need to develop a certain kind of intuition to
attack these problems. I very much recommend the new documentation page
http://doc.akka.io/docs/akka-stream-and-http-experimental/1.0/scala/stream-composition.html
as it helps to visualize the ideas.
I created
Hi Luc,
in the new dump there are again these two connections:
port 59385 - 57649
and
port 59386 - 8080
It looks as if you are running some kind of transparent proxy (a
desktop firewall sofware?) that redirects all the traffic through a
middleman. So, if you look at the connection from 59385
Hi John,
yes, this is called PathMachers.segment() (to be consistent with the Scala
side). It may make sense to create an alias or have another look at the
names in general to see if they can be made more consistent.
Johannes
On Wednesday, July 29, 2015 at 7:06:16 AM UTC+2, john@gmail.com
And now I added another version where the server just streams random
numbers until the client disconnects, then it closes the connection. It
needed a custom stage though to make emitting from an Iterable
interruptible (mapConcat does not interrupt on completion, only on errors).
On Wed, Jul 29,
For those who are interested, I have just cut the second major release of the
Requester library https://github.com/jducoeur/Requester, with many
improvements over 1.1.
*What it is:* Requester introduces request(), which can be thought of as
the better-behaved big brother to ask(). ask() returns
12 matches
Mail list logo
