[akka-user] Re: Can't execute more than 4 requests in parallel

[Andrew Gaydenko]

May be without client ?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: [ANNOUNCE] Announcing the new Akka Team Blog (Let it Crash!)

[Andrew Gaydenko]

Thanks! 
At that moment for some reason Firefox hasn't found the refs. Now it does. 
Sorry for noise.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: [ANNOUNCE] Announcing the new Akka Team Blog (Let it Crash!)

[Andrew Gaydenko]

Great! Any chance for RSS?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: ANNOUNCE: New Remoting Milestone 2

[Andrew Gaydenko]

Roland, thanks  - all is absolutely clear now! :)

On Saturday, June 11, 2016 at 2:20:48 PM UTC+3, rkuhn wrote:
>
> Andrew,
>
> there seem to be a few misunderstandings here:
>
>
>- HTTP by design requires TCP as its transport
>- akka-http implements HTTP using akka-streams which in turn uses Akka 
>IO for the TCP part—no Netty anywhere
>- akka-remote has nothing to do with Akka IO, akka-stream, or akka-http
>
>
> Regards,
>
> Roland
>
> 11 juni 2016 kl. 12:58 skrev Andrew Gaydenko  >:
>
> Patrik, sorry I wasn't clear. If my guess is valid, at the moment 
> akka-http is using TCP/Netty transport provided by akka-remote. As far as 
> you are introducing new light-speed transport for remote, what are the 
> plans wrt netty transport used for http? Is it going to just be kept 
> intact? Or - I'm just wrong with my guess :)
>
> On Saturday, June 11, 2016 at 12:42:30 PM UTC+3, Patrik Nordwall wrote:
>>
>> I'm not sure I understand the context of the question? Are you looking 
>> for Akka Remoting (actor messaging) over TCP or are you just curious in 
>> general of any plans for Akka Http transport, such as HTTP/2?
>>
>> fre 10 juni 2016 kl. 19:10 skrev Andrew Gaydenko :
>>
>>> Patrik,
>>>
>>> In the Aeron-as-a-transport context (UDP) what is the akka-http's 
>>> transport (TCP) planned future?
>>>
>>>
>>> On Friday, June 10, 2016 at 6:46:09 PM UTC+3, Patrik Nordwall wrote:
>>>>
>>>> Dear hakkers,
>>>>
>>>> We’re excited to announce that we have released the second development 
>>>> milestone of the new Akka Remoting, which has the code named Artery. It’s 
>>>> an early development preview and we encourage you to try it out and give 
>>>> us 
>>>> feedback, but it’s not intended for production usage yet.
>>>>
>>>> The version number is 2.4-ARTERY-M2 with same artifacts as usual. 
>>>>
>>>> It is enabled with the following configuration:
>>>>
>>>> akka.remote.artery {
>>>>  enabled = on
>>>>  # The hostname or ip clients should connect to.
>>>>  hostname = localhost
>>>>  # use 0 if you want a random available port
>>>>  port = 20200
>>>> }
>>>>
>>>> The protocol part of the actor system address is artery (*), so you 
>>>> need to change previous akka.tcp to artery in for example 
>>>> configuration of cluster seed-nodes.
>>>>
>>>> A summary of what is included in M2 compared to M1 
>>>> <https://groups.google.com/d/msg/akka-user/z05q9-cEULw/qCJqqYlwAAAJ>:
>>>>
>>>>
>>>>- performance improvements
>>>>- initial flight recorder to capture low and high frequency events 
>>>>in memory mapped files for debugging (also production issues) and 
>>>> testing
>>>>- make it possible to use efficient serialization with ByteBuffers 
>>>>directly
>>>>- various bug fixes, including issues with remote deployment
>>>>- test coverage by porting most of the old remoting tests
>>>>
>>>>
>>>> The full list of changes since the last milestone is available under 
>>>> the 2.4-ARTERY-M2 
>>>> <https://github.com/akka/akka/issues?q=milestone%3A2.4-ARTERY-M2+is%3Aclosed>
>>>>  
>>>> milestone on github for your reference.
>>>>
>>>> We are using Aeron <https://github.com/real-logic/Aeron> as the 
>>>> underlying transport and are implementing the layers on top using Akka 
>>>> Streams. You find more details in the design document 
>>>> <https://github.com/akka/akka-meta/issues/16>.
>>>>
>>>> The development branch is artery-dev 
>>>> <https://github.com/akka/akka/tree/artery-dev>, in case you want to 
>>>> take a look or contribute. Issues are labeled with t:remoting:artery 
>>>> <https://github.com/akka/akka/issues?q=is%3Aopen+is%3Aissue+label%3At%3Aremoting%3Aartery>
>>>> .
>>>>
>>>> (*) The protocol name is not final and may change before the new 
>>>> remoting infrastructure goes stable.
>>>>
>>>> -- 
>>>>
>>>> Patrik Nordwall
>>>> Akka Tech Lead
>>>> Lightbend <http://www.lightbend.com/> -  Reactive apps on the JVM
>>>> Twitter: @patriknw
>>>>
>>>>

Re: [akka-user] Re: ANNOUNCE: New Remoting Milestone 2

[Andrew Gaydenko]

Patrik, sorry I wasn't clear. If my guess is valid, at the moment akka-http 
is using TCP/Netty transport provided by akka-remote. As far as you are 
introducing new light-speed transport for remote, what are the plans wrt 
netty transport used for http? Is it going to just be kept intact? Or - I'm 
just wrong with my guess :)

On Saturday, June 11, 2016 at 12:42:30 PM UTC+3, Patrik Nordwall wrote:
>
> I'm not sure I understand the context of the question? Are you looking for 
> Akka Remoting (actor messaging) over TCP or are you just curious in general 
> of any plans for Akka Http transport, such as HTTP/2?
>
> fre 10 juni 2016 kl. 19:10 skrev Andrew Gaydenko  >:
>
>> Patrik,
>>
>> In the Aeron-as-a-transport context (UDP) what is the akka-http's 
>> transport (TCP) planned future?
>>
>>
>> On Friday, June 10, 2016 at 6:46:09 PM UTC+3, Patrik Nordwall wrote:
>>>
>>> Dear hakkers,
>>>
>>> We’re excited to announce that we have released the second development 
>>> milestone of the new Akka Remoting, which has the code named Artery. It’s 
>>> an early development preview and we encourage you to try it out and give us 
>>> feedback, but it’s not intended for production usage yet.
>>>
>>> The version number is 2.4-ARTERY-M2 with same artifacts as usual. 
>>>
>>> It is enabled with the following configuration:
>>>
>>> akka.remote.artery {
>>>
>>>  enabled = on
>>>
>>>  # The hostname or ip clients should connect to.
>>>
>>>  hostname = localhost
>>>
>>>  # use 0 if you want a random available port
>>>
>>>  port = 20200
>>>
>>> }
>>>
>>> The protocol part of the actor system address is artery (*), so you 
>>> need to change previous akka.tcp to artery in for example configuration 
>>> of cluster seed-nodes.
>>>
>>> A summary of what is included in M2 compared to M1 
>>> <https://groups.google.com/d/msg/akka-user/z05q9-cEULw/qCJqqYlwAAAJ>:
>>>
>>>
>>>- 
>>>
>>>performance improvements
>>>- 
>>>
>>>initial flight recorder to capture low and high frequency events in 
>>>memory mapped files for debugging (also production issues) and testing
>>>- 
>>>
>>>make it possible to use efficient serialization with ByteBuffers 
>>>directly
>>>- 
>>>
>>>various bug fixes, including issues with remote deployment
>>>- 
>>>
>>>test coverage by porting most of the old remoting tests
>>>
>>>
>>> The full list of changes since the last milestone is available under the 
>>> 2.4-ARTERY-M2 
>>> <https://github.com/akka/akka/issues?q=milestone%3A2.4-ARTERY-M2+is%3Aclosed>
>>>  
>>> milestone on github for your reference.
>>>
>>> We are using Aeron <https://github.com/real-logic/Aeron> as the 
>>> underlying transport and are implementing the layers on top using Akka 
>>> Streams. You find more details in the design document 
>>> <https://github.com/akka/akka-meta/issues/16>.
>>>
>>> The development branch is artery-dev 
>>> <https://github.com/akka/akka/tree/artery-dev>, in case you want to 
>>> take a look or contribute. Issues are labeled with t:remoting:artery 
>>> <https://github.com/akka/akka/issues?q=is%3Aopen+is%3Aissue+label%3At%3Aremoting%3Aartery>
>>> .
>>>
>>> (*) The protocol name is not final and may change before the new 
>>> remoting infrastructure goes stable.
>>>
>>> -- 
>>>
>>> Patrik Nordwall
>>> Akka Tech Lead
>>> Lightbend <http://www.lightbend.com/> -  Reactive apps on the JVM
>>> Twitter: @patriknw
>>>
>>> -- 
>> >>>>>>>>>> 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 akka-user+...@googlegroups.com .
>> To post to this group, send email to akka...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
>>>>>>>>>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: ANNOUNCE: New Remoting Milestone 2

[Andrew Gaydenko]

Patrik,

In the Aeron-as-a-transport context (UDP) what is the akka-http's transport 
(TCP) planned future?

On Friday, June 10, 2016 at 6:46:09 PM UTC+3, Patrik Nordwall wrote:
>
> Dear hakkers,
>
> We’re excited to announce that we have released the second development 
> milestone of the new Akka Remoting, which has the code named Artery. It’s 
> an early development preview and we encourage you to try it out and give us 
> feedback, but it’s not intended for production usage yet.
>
> The version number is 2.4-ARTERY-M2 with same artifacts as usual. 
>
> It is enabled with the following configuration:
>
> akka.remote.artery {
>
>  enabled = on
>
>  # The hostname or ip clients should connect to.
>
>  hostname = localhost
>
>  # use 0 if you want a random available port
>
>  port = 20200
>
> }
>
> The protocol part of the actor system address is artery (*), so you need 
> to change previous akka.tcp to artery in for example configuration of 
> cluster seed-nodes.
>
> A summary of what is included in M2 compared to M1 
> :
>
>
>- 
>
>performance improvements
>- 
>
>initial flight recorder to capture low and high frequency events in 
>memory mapped files for debugging (also production issues) and testing
>- 
>
>make it possible to use efficient serialization with ByteBuffers 
>directly
>- 
>
>various bug fixes, including issues with remote deployment
>- 
>
>test coverage by porting most of the old remoting tests
>
>
> The full list of changes since the last milestone is available under the 
> 2.4-ARTERY-M2 
>  
> milestone on github for your reference.
>
> We are using Aeron  as the 
> underlying transport and are implementing the layers on top using Akka 
> Streams. You find more details in the design document 
> .
>
> The development branch is artery-dev 
> , in case you want to take 
> a look or contribute. Issues are labeled with t:remoting:artery 
> 
> .
>
> (*) The protocol name is not final and may change before the new remoting 
> infrastructure goes stable.
>
> -- 
>
> Patrik Nordwall
> Akka Tech Lead
> Lightbend  -  Reactive apps on the JVM
> Twitter: @patriknw
>
>

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka HTTP performance for short lived connections

[Andrew Gaydenko]

Adam, thanks!

Very informative. I also have found handy to use almost empty response to 
estimate the whole request-response chain itself (starting from now 
abandoned tiscaf [1] and rising rps up to almost 90K on humble workstation 
:) ).

[1] http://gaydenko.com/scala/tiscaf/httpd/

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka HTTP performance for short lived connections

[Andrew Gaydenko]

Adam, just curious, can you, please, supply some example ApacheBench output?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

Giovanni, hi!

With some piece of stubbornness :) I (guess) have found a way with 
Source.last():

  def sinkFoldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]] = 
Sink.fromGraph {
val last = Sink.last[U]

GraphDSL.create(last) { implicit b => last =>
  import GraphDSL.Implicits._
  val zip = b.add(ZipWith(f))
  val bcast = b.add(Broadcast[U](2))
  val merge = b.add(Merge[U](2))

  Source.single(zero) ~> merge ~> bcast ~> last
  bcast ~> zip.in0
  zip.out.mapAsync(1)(identity) ~> merge

  SinkShape(zip.in1)
}
  }

And in hands I have got a task with needing to fold starting with future 
zero. So, I have tried:

  def sinkFoldMM[U, T](zeroFu: Future[U])(f: (U, T) ⇒ Future[U]): Sink[T, 
Future[U]] = Sink.fromGraph {
val last = Sink.last[U]

GraphDSL.create(last) { implicit b => last =>
  import GraphDSL.Implicits._
  val zip = b.add(ZipWith(f))
  val bcast = b.add(Broadcast[U](2))
  val merge = b.add(Merge[U](2))

  Source.fromFuture(zeroFu) ~> merge ~> bcast ~> last
  bcast ~> zip.in0
  zip.out.mapAsync(1)(identity) ~> merge

  SinkShape(zip.in1)
}
  }

By some reason this test

  val upTo = 2000;
  //val upTo = 0;
  val result = Source(0 until upTo).runWith(sinkFoldMM(Future(0))((a, x) => 
Future(a + x)))

  println(Await.result(result, 10.minutes))
  sys.exit(0)

takes two times more CPU time in comparison with sinkFoldM (~50 second vs. 
~25 second).


-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: [2.5-Scala] How to cleanup Sink/Source?

[Andrew Gaydenko]

Or, if to reformulate, how does transparent stage look?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: [2.5-Scala] How to cleanup Sink/Source?

[Andrew Gaydenko]

Johan, hi!

Sorry, haven't grokked exactly :) 
Do I understand correctly, in code above I must eliminate all 
complete()/cancel() calls, instead just bothering about own clean up only?
In other words, are `finish` events propagating to other stages 
independently these my stage's in/out handlers?

On Friday, March 11, 2016 at 4:45:39 PM UTC+3, Akka Team wrote:
>
> In general the sources and sinks should take care of cleaning up 
> themselves rather than have some downstream/upstream element report 
> cancel/failure/completion through a side channel, if you are implementing a 
> custom Source it's OutHandler will get a onDownstreamFinish and if your 
> are writing a Sink its InHandler will get onUpstreamFinish and 
> onUpstreamFailure where closing resources can be done. 
>
> Think of their resources as internal mutable state just like in an actor. 
> It is not another components responsibility to manage such resources.
>
> --
> Johan Andrén
> Akka Team, Lightbend Inc.
>

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

On Wednesday, March 9, 2016 at 1:20:37 PM UTC+3, Giovanni Alberto 
Caporaletti wrote:
>
> It would fail with an empty stream. You can use lastOption but you would 
> need to map over the materialized value thus needing an execution context 
> outside the stream context.
>

Oh.. Yes! Thanks for pointing out.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

Giovanni, I mean your last suggestion with custom stage.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

Giovanni, hi!

What do you think about replacing

val sink = Sink.fold(zero)(Keep.right[U, U])

with

val sink = Sink.last[U]


?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: change of Tech Lead

[Andrew Gaydenko]

Roland,

Thanks for your help here, in the group! - for some magic reason you are 
just the best in understanding my ugly, vague questions. Good luck!

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

Giovanni, hi!

Thanks! - have played with this test. In fact, I started tests with 
-Xmx=128M, and range up to 20M. The first two variants resulted in OOME, as 
Roland predicted, and the last one with own Graph resulted in the rather 
quick answer with small RAM footprint during execution (~100MB on system 
monitor) - as you waned :)

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

On Sunday, March 6, 2016 at 2:28:22 AM UTC+3, Giovanni Alberto Caporaletti 
wrote:
>
> Hi Roland,
> you're right, my solution was a bit naive. I came up with this, I'm pretty 
> sure it can be done in a better way, looking forward to seeing your 
> solution :)
>

Giovanni, thanks for this graph - I use as example on reading streams doc :)
Have you idea how to provoke those "unbounded amounts of futures without 
back pressure" Roland has wrote about? - to get OOME or.. what?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: [2.5-Scala] How to cleanup Sink/Source?

[Andrew Gaydenko]

Or - must the last method be

  override def onDownstreamFinish(): Unit = {
cancel(in)
onDownFinish
  }

?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: [2.5-Scala] How to cleanup Sink/Source?

[Andrew Gaydenko]

At the moment I have got this approach. Let's define a stage:

class OnFinish[A] extends GraphStage[FlowShape[A, A]] {

  def onUpFinish: Unit = {}
  def onDownFinish: Unit = {}

  val in = Inlet[A]("onFinish.in")
  val out = Outlet[A]("onFinish.out")

  override val shape = FlowShape.of(in, out)

  override def createLogic(attr: Attributes): GraphStageLogic = new 
GraphStageLogic(shape) {

setHandler(in, new InHandler {
  override def onPush(): Unit = push(out, grab(in))

  override def onUpstreamFinish(): Unit = {
complete(out)
onUpFinish
  }
})

setHandler(out, new OutHandler {
  override def onPull(): Unit = pull(in)
  override def onDownstreamFinish(): Unit = {
complete(out)
onDownFinish
  }
})
  }
}

Now, let's use it for source:

  private lazy val flow = Flow.fromGraph(new OnFinish[ByteString] {
override def onUpFinish: Unit = cleanup
  })
  private lazy val finalSrc = src.via(flow)

At the use case in hands I have got what I wanted. But is this approach 
correct in general?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

Roland, hi!

Thanks for pointing the problem out! 
So we'll stay with hope for Future[ProperSolution] :)

Another approach I have tried is to use the same (as in the first 
suggestion above) folding function, but to unwrap from extra Future via 
flatMap(identity) streaming result after run. Sometimes this way isn't 
handy as far as it reduces possible interaction ways between code parts. At 
any case, is this way also affected by the issue?

On Saturday, March 5, 2016 at 11:52:06 PM UTC+3, rkuhn wrote:
>
> Unfortunately these solutions create unbounded amounts of futures without 
> back pressure, so I'd recommend against this approach. But it is late and 
> I'm on the phone so cannot suggest a proper solution.
>
> Regards,
>
> Roland 
>
> Sent from my iPhone
>
> On 05 Mar 2016, at 17:41, Giovanni Alberto Caporaletti  > wrote:
>
> how about this:
>
> def foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]] = {
>   Sink
> .fold[Future[U], T](Future.successful(zero))((fu, t) => fu.flatMap(f(_, 
> t)))
> .mapMaterializedValue(_ flatMap identity)
> }
>
> or this:
>
> def foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]] = {
>   Flow[T]
> .fold(Future.successful(zero))((fu, t) => fu.flatMap(f(_, t)))
> .mapAsync(1)(identity)
> .toMat(Sink.head)(Keep.right)
> }
>
>
>
> On Saturday, 5 March 2016 17:00:08 UTC+1, Andrew Gaydenko wrote:
>>
>> Hi! There is 
>>
>> f: (U, T) ⇒ Future[U] 
>>
>> rather than 
>>
>> f: (U, T) ⇒ U
>>
>> in hands. How to create 
>>
>> Sink[T, Future[U]]
>>
>> ?
>>
> -- 
> >>>>>>>>>> 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 akka-user+...@googlegroups.com .
> To post to this group, send email to akka...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
>>>>>>>>>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

On Saturday, March 5, 2016 at 11:52:06 PM UTC+3, rkuhn wrote:
>
> Unfortunately these solutions create unbounded amounts of futures without 
> back pressure, so I'd recommend against this approach. But it is late and 
> I'm on the phone so cannot suggest a proper solution.
>

Roland, hi!

Thanks for pointing the problem out! 
So we'll stay with hope for Future[ProperSolution] :)

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] [2.5-Scala] How to cleanup Sink/Source?

[Andrew Gaydenko]

HI!

I'm playing with Play projects migrating them to v.2.5.0. Play's Iteratee 
and Enumerator have got some means to cleanup streams (Input.EOF and 
onDoneEnumeratiing() appropriately). So, what is that obvious way :) to 
cleanup sources and sinks in Akka Stream?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

Giovanni, hi!

I used a way similar to the the first suggestion, but wasn't sure it is 
elegant way to wrap zero into Future on rewriting folding function.
So, I'll experiment with both ways when some benchmarks be ready. And I 
need some time to dig in the second suggestion :)

Thanks!!

On Saturday, March 5, 2016 at 7:41:18 PM UTC+3, Giovanni Alberto 
Caporaletti wrote:
>
> how about this:
>
> def foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]] = {
>   Sink
> .fold[Future[U], T](Future.successful(zero))((fu, t) => fu.flatMap(f(_, 
> t)))
> .mapMaterializedValue(_ flatMap identity)
> }
>
> or this:
>
> def foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]] = {
>   Flow[T]
> .fold(Future.successful(zero))((fu, t) => fu.flatMap(f(_, t)))
> .mapAsync(1)(identity)
> .toMat(Sink.head)(Keep.right)
> }
>
>
>
> On Saturday, 5 March 2016 17:00:08 UTC+1, Andrew Gaydenko wrote:
>>
>> Hi! There is 
>>
>> f: (U, T) ⇒ Future[U] 
>>
>> rather than 
>>
>> f: (U, T) ⇒ U
>>
>> in hands. How to create 
>>
>> Sink[T, Future[U]]
>>
>> ?
>>
>

-- 
>>>>>>>>>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] How to? - Sink.foldM[U, T](zero: U)(f: (U, T) ⇒ Future[U]): Sink[T, Future[U]]

[Andrew Gaydenko]

Hi! There is 

f: (U, T) ⇒ Future[U] 

rather than 

f: (U, T) ⇒ U

in hands. How to create 

Sink[T, Future[U]]

?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: ANNOUNCE: Akka Streams & HTTP 2.0.2 Released!

[Andrew Gaydenko]

On Friday, January 15, 2016 at 9:15:49 AM UTC+3, Patrik Nordwall wrote:
>
> Play is compatible with Akka 2.4 and Akka Streams 1.0. There will soon be 
> a new Play 2.5 milestone that is compatible with Akka Stream 2.0.
>
> If you have found something that Play is not compatible with Akka 2.4 we 
> would be interested in the details.
>

Yes, I have tried and all is OK with Play + Akka 2.4. It was my mistake, 
sorry.

I have dug in the problem (method not found) and have found Akka 2.4 be 
incompatible with... Scala! He-he... It's a joke. Mostly... :) The thing 
is, I use custom script to start applications which uses scala official 
script rather just raw java. It resulted in using jars (with akka-actor 
2.3.10 among them) in lib directory from the official Scala distribution. 
Bang!..

After switching to java script problems have gone.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: ANNOUNCE: Akka Streams & HTTP 2.0.2 Released!

[Andrew Gaydenko]

On Friday, January 15, 2016 at 9:15:49 AM UTC+3, Patrik Nordwall wrote:
>
> Play is compatible with Akka 2.4 and Akka Streams 1.0. There will soon be 
> a new Play 2.5 milestone that is compatible with Akka Stream 2.0.
>

I mean context when streams (2.x at the momemnt) are used in their own, 
regardless Play.
 

> If you have found something that Play is not compatible with Akka 2.4 we 
> would be interested in the details.
>

OK, I'll report as soon as find an opportunity to try again.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: ANNOUNCE: Akka Streams & HTTP 2.0.2 Released!

[Andrew Gaydenko]

On Thursday, January 14, 2016 at 11:44:37 PM UTC+3, Konrad Malawski wrote:
>
> Meanwhile, we have moved all new Streams & HTTP development to the master 
> branch, which means that these, as previously announced, will very soon 
> become part of Akka 2.4
>

How fast are you going to be? The thing is I have tried to switch to Akka 
2.4 but have found the last Play not to be compatible with Akka 2.4 (sorry, 
I don't remember details now). So at the moment I'm forced to used Akka 
2.3, and streams separation is the only way.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka Stream and Http 2.0-M1 Released!

[Andrew Gaydenko]

Konrad, hi!

Thanks for the explanation, now i see the M1 is more interesting (for me) 
than it can be visible at first :) I remember the Play team intention to 
(officially, not experimental) switch to Akka Stream from Iteratees only 
when performance will be comparable. So, that future is moving to reality, 
great!

On Saturday, November 7, 2015 at 8:15:55 PM UTC+3, Konrad Malawski wrote:
>
> Hi Andrew,
> it is the most important step – fusing is *the* feature to enable high 
> throughput + single materialization (per request) for Akka HTTP.
> The feature in 2.0-M1 allows to to apply the fusing on fan-out and fan-in 
> operations (we could do it previously for linear stages),
> so it is a major step towards the promised performance improvements.
>
> Actually enabling fusing on parts of the HTTP pipeline will be the next 
> step, which will then make a noticeable impact on perf.
>
> Hope this explains things!
>
> -- Konrad
>
>

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka Stream and Http 2.0-M1 Released!

[Andrew Gaydenko]

Great!

On Friday, November 6, 2015 at 4:19:49 PM UTC+3, Martynas Mickevičius wrote:
>
> ... This is also the feature that will increase performance for various 
> use cases, including HTTP.
>

Is it just the first step, or significant part of the way, or almost the 
whole way to make Akka HTTP comparable with Play/Iteratee HTTP 
implementation in terms of performance?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] filePath + encoding = Source[Char, _] - How to?

[Andrew Gaydenko]

Hi!

In fact the use case in hands demands Source[String, _], where element is a 
string with length limited by given max. But is can be got from char sink 
with grouped stage.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] not-experimental streams?

[Andrew Gaydenko]

On Tuesday, September 22, 2015 at 12:57:19 PM UTC+3, Patrik Nordwall wrote:
>
> We are confident that Akka Streams will be successful.
>

Great, thanks for the clarification!

>

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] not-experimental streams?

[Andrew Gaydenko]

Hi!

Why streams are still named as experimental? Is there still an opportunity 
current streams API will share pipelines' destiny? :)

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: The best ways to resolve future inside an actor?

[Andrew Gaydenko]

Дмитрий,

In this topic

https://groups.google.com/forum/#!folder/current/akka-user/R1ZxPKlp1fI

*Michael Frank* has suggested an idea, I have implemented it, and it does 
work at my use case as expected. Probably, you will get something useful 
there also :)

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: Piping + gracefull shutdown: is it possible?

[Andrew Gaydenko]

Michael,

I have implemented the idea in my context. Yes, it does work. Thanks again!

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: Piping + gracefull shutdown: is it possible?

[Andrew Gaydenko]

On Monday, May 18, 2015 at 9:33:28 PM UTC+3, Michael Frank wrote:
>
> i usually solve this by map()ing the future to some request id that i 
> generate.  for example (written on the spot, may not compile)
>

Michael,

Aha, I see, it's very smart. Will try. Thanks!

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: Piping + gracefull shutdown: is it possible?

[Andrew Gaydenko]

On Monday, May 18, 2015 at 7:51:31 PM UTC+3, Michael Frank wrote:
>
> How about piping the result of the future back to actor1, then send the 
> result to actor2?  you can prune the completed future in actor1 when it 
> receives the result.
>

Michael, how does actor1 discover that future returned result is connected 
to?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Piping + gracefull shutdown: is it possible?

[Andrew Gaydenko]

Magnus, hi!

Thanks for the suggestions!

On Monday, May 18, 2015 at 3:57:00 PM UTC+3, Magnus Andersson wrote: 

>
>1. Keep track of running futures in your actor1 in a var. When your 
>actor enters poststop you can await the completion of all referenced 
>futures. You probably would have to adjust so that after piping the 
> message 
>to actor2 you also remove the reference to the future.
>
>  I'm trying to implement it just now. To keep collection holding 
uncompleted futures limited I must cleanup the collection (say, on every 
new message received). The only way is to use fu.isCompleted, and official 
documentation says it will result in non deterministic flow. So, I'm in 
doubt. What do you think?

>
>1. Spawn a new child actor for this specific task instead of using a 
>future. Your task is now part of the actor life cycle and will be a child 
>to your actor1. The actor will have to terminate itself upon completing 
> the 
>task.
>
> Unfortunately, the task returning future is a call to external library 
API, so I can not redesign it.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Piping + gracefull shutdown: is it possible?

[Andrew Gaydenko]

HI! 

Say, we have actor1 calling a function on received message returning 
Future[T]. 
Then this actor1 pipes the future to actor2. 
And the last one does some final work on T. 

I have not found a way to gracefully shutdown such actor system (say, with 
attached shutdown 
hook for daemonic actor system) having in hands a demand to process already 
piped messages
(that is to complete all generated futures).

Have you?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: The best ways to resolve future inside an actor?

[Andrew Gaydenko]

OK, let's take a suggestion and use piping. So, say, we have actor1 (for 
example, with RoundRobin(1)). calling a function on received message 
returning Future, and this actor1 pipes the future to actor2 (for example, 
with RoundRobin(5)). And the last one does some final work. I have not 
found a way to gracefully shutdown such actor system having in hands a 
demand to process already sent messages (that is to complete all generated 
futures). Have you?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: The best ways to resolve future inside an actor?

[Andrew Gaydenko]

Дмитрий.

Will it look simpler would we add dedicated actor to pipe to? I have tried 
this way. The problem at my case is a function returns Future limited with 
timeout, and time starts to tick too early resulting in multiple timeouts 
(while the dumb way with awaiting doesn't result in any errors).

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: The best ways to resolve future inside an actor?

[Andrew Gaydenko]

On Thursday, May 14, 2015 at 8:46:27 PM UTC+3, Patrik Nordwall wrote:
>
> If there are no relationship (no ordering) between the future result and 
> other incoming messages you can just use pipe, without stash.
>

Let's assume at the moment we have:

def receive = {
  case Msg(data) =>
def job = callReturningFuture(data)(context.dispatcher)
Await.result(job, 1000.millis)
}

What is the suggestion?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: The best ways to resolve future inside an actor?

[Andrew Gaydenko]

On Thursday, May 14, 2015 at 8:04:50 PM UTC+3, √ wrote:
>
> What if it never completes?
>

Timeout is acceptable.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: The best ways to resolve future inside an actor?

[Andrew Gaydenko]

Sequence order isn't a problem. RondRobinPool(1) here isn't more rather 
just a limiting CPU consumption to a single core. As at the first message 
in the topic, the problem is to gracefully call function returning Future 
inside a message handler. We don't want answering to sender, don't want to 
serialize per se.. Just are looking for the best way to resolve a Future 
inside a receive/case message handler.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: The best ways to resolve future inside an actor?

[Andrew Gaydenko]

On Thursday, May 14, 2015 at 1:41:30 PM UTC+3, rrodseth wrote:
>
> Have you looked at the pipeTo pattern and the Stash trait? I'm not sure 
> why a combination of pipeTo and become() with Stash wouldn't work.
>

What is that relation between stashing and piping with resolving a future? 
Can you, please, explain in code?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: The best ways to resolve future inside an actor?

[Andrew Gaydenko]

It's funny just now I have met the same situation! :) 

More strictly, my case is even simpler as far as an actor hasn't got state. 
I also use RoundRobinPool(1) to force serialization. I have tried just to 
use Await.result(), and it seems to work . To call function returning Future  
I use context.dispatcher as execution context. 

OTOH, there is a common recommendation to avoid awaiting. So, what is the 
best practice here?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] draining daemon system actors' queues on shutdown

[Andrew Gaydenko]

Konrad, great, thanks! - will dig in...

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: draining daemon system actors' queues on shutdown

[Andrew Gaydenko]

I must clarify saying "draining" I mean giving to all system's actors some 
duration to process all already sent messages.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] draining daemon system actors' queues on shutdown

[Andrew Gaydenko]

How to drain daemon system actors' queues on system exit?

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] There are now akka-stream in master. Why?

[Andrew Gaydenko]

On Sunday, June 1, 2014 7:42:49 PM UTC+4, Konrad Malawski wrote:
>
> Yes, perhaps I should explain our current workflow with these branches 
> actually:
>
> master will eventually become akka 2.4.x
>
> release-2.3 will eventually become akka 2.3.4 (and 2.3.5 if it’s needed 
> etc).
>
> release-2.3-dev is used only for streams development. It is separate to 
> keep iterating / releasing streams faster than the main akka 2.3. 
>  It will be merged to release-2.3 once we decide they’re ready to roll-in.
>
> Needed changes from 2.3 will be ported to 2.4 (master), of course at some 
> point.
>
> I hope this helps!
>

Yes, absolutely, thanks!

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] There are now akka-stream in master. Why?

[Andrew Gaydenko]

Aha, thanks, I see, it's just a way to organize branches. 

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: There are now akka-stream in master. Why?

[Andrew Gaydenko]

Sorry, my mistake, I mean "There are *no* akka-stream...". I haven't found 
a way to edit the subject.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] There are now akka-stream in master. Why?

[Andrew Gaydenko]

I just have noticed master hasn't anymore akka-stream subproject. Does it 
mean akka (and Scala in whole) reactive streaming is preparing for the next 
reincarnation? :)

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka Streams Preview is Available

[Andrew Gaydenko]

On Thursday, April 17, 2014 11:30:22 AM UTC+4, rkuhn wrote:
>
> e also have prepared an Activator 
> template with 
> which you can start exploring the 
> API.
>  
>
>

I want more! - TCP streams with custom msg <-> byte buffer 
encoding/decoding, rechunking in accordance with max length, and so on :)

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-dev] Re: [akka-user] Akka IO Pipelines going away

[Andrew Gaydenko]

On Tuesday, April 8, 2014 6:27:44 PM UTC+4, √ wrote:
>
> Well said, Roland.
>

Being one of removal-affected Akka users, at the moment I have just moved 
to netty.io during a couple of days (custom protocol with ~ dozen 
messages). Knowing main pipeline architecture ideas it was really easy 
migration. So, yes, using not yet mature software (pieces) is my decision, 
and. as a result, it is my responsibility to repair such situation as we 
have with Akka's pipelines.

To my taste any decision to remove something is - averaging - much better 
rather a decision to add something. I know it for sure! :) As a result, I 
haven't got any technical or moral discomfort related with the team 
decision. I hope everybody can share with me this soft point of view.

-- 
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Has anything been published about the Reactive Streams design?

[Andrew Gaydenko]

There were (now deprecated) pipelines borrowed from spray 
https://groups.google.com/forum/#!starred/akka-user/8fZ75MlVEYc So the team 
is preparing something new and tasty for April. You are the second in the 
waiting queue as far as I'm the first :)

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: http://akka.io/faq/
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [akka-user] Akka IO Pipelines going away

[Andrew Gaydenko]

Great, I'll be :)

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: http://akka.io/faq/
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [akka-user] Akka IO Pipelines going away

[Andrew Gaydenko]

On Wednesday, January 22, 2014 11:21:46 AM UTC+4, rkuhn wrote:
>
> We know that people have been running their business on a 1.0 milestone of 
> Akka, or used the experimental Cluster successfully, and this has maybe led 
> to the expectation that even our experiments are highly reliable—which we 
> feel honored by—but the truth is that in fact some things do not turn out 
> well enough after all.
>

Have the Akka team already got some concrete pipelines replacement (with 
estimation of introducing date) in mind? The thing is, a project under 
development isn't in production yet, so I have some time frame (few months) 
to switch from pipelines to something more official :) And I'm not afraid 
of beta state. 

Or - what is the best current way for data streaming?

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: http://akka.io/faq/
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/groups/opt_out.

[akka-user] Re: What happend to the IO stack between 2.3M2 and 2.3RC1 ???

[Andrew Gaydenko]

https://groups.google.com/forum/#!topic/akka-user/8fZ75MlVEYc

On Tuesday, January 21, 2014 8:15:38 PM UTC+4, Cédric Munger wrote:
>
> Hello,
>
> I've started to migrate from 2.3.M2 API to the RC1 and I have some very 
> bad surprises on the IO API side.
> It looks like you've removed a LOT of things here is a list of classes 
> that are missing between M2 and RC1 :
>
> akka.io.AbstractSymmetricPipePair;
> akka.io.PipePairFactory;
> akka.io.SymmetricPipePair;
> akka.io.SymmetricPipelineStage;
> akka.io.BackpressureBuffer.*;
> akka.io.PipelineStage;
> akka.io.TcpPipelineHandler.*;
> akka.io.TcpReadWriteAdapter;
>
> We have build a lots of things around theses classes with your new IO 
> stack.
> Do I have to understand that we have to trash weeks of work and rewrite 
> everything
> or do you have a package that still supports these classes ?
>
> Regards
>
> C.Munger
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: http://akka.io/faq/
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/groups/opt_out.

[akka-user] Re: ANNOUNCE: Akka 2.3.0-RC1 (RELEASE CANDIDATE)

[Andrew Gaydenko]

So 2.3.0 will be released without IO at all. Have I missed something?

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: http://akka.io/faq/
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/groups/opt_out.

[akka-user] Re: Akka IO Pipelines going away

[Andrew Gaydenko]

Roland,

I have a part of some big project based on pipelines. Is it possible to 
roughly denote that time points of pipelines removing and new streams 
introducing? Will there be some time frame these technologies be existing 
in parallel? - to have an opportunity to smoothly switch a code base: pipes 
still exist, and new streams are at least close to release.


-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: http://akka.io/faq/
>>  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 akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/groups/opt_out.