the Cluster would
be inappropriate.
Thanks,
Daniel Armak
On Wed, Feb 24, 2016 at 6:55 PM, Konrad Malawski <kt...@lightbend.com>
wrote:
> Yeah, for example if irrecoverable loss of system messages happens.
> In general death watch on Actors using remoting can in failure scenarios
> (
I can't comment on akka-http, but here's my understanding of the HTTP spec.
It's certainly legal to send a response before receiving the request
entity, but the client isn't obligated to start reading the response before
it finishes sending the request. And if the server closes the connection
cannot?
Thanks!
--
Daniel Armak
--
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
a generic implementation of RS, would you have used
it? What would you want from such a library?
Thanks,
--
Daniel Armak
--
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
management and back-pressure implemented in the library.
It's a good fit for me, but would it be good for others? I don't know.
Daniel Armak
On Wed, Oct 29, 2014 at 12:29 PM, Akka Team akka.offic...@gmail.com wrote:
On Wed, Oct 29, 2014 at 11:17 AM, Roland Kuhn goo...@rkuhn.info wrote:
What
to implement RS directly. I'm pretty sure the
RS specification authors didn't intend for that to happen :-)
Daniel Armak
On Wed, Oct 29, 2014 at 3:02 PM, Michał Kiędyś mic...@kiedys.net wrote:
Hi Daniel,
I made my anwser below. Your opinion is valuable for me and I would like
you get code review from
Play is a *web* framework. It includes support for lots of
web-related features that aren't part of HTTP as such.
Daniel Armak
On Tue, Oct 14, 2014 at 12:11 PM, Prakhyat Mallikarjun
prakhyat...@gmail.com wrote:
Hi Konrad,
I am aware of these posts.
Since we are in stage of planning
Right, I forgot spray doesn't have a Java API. Sorry about not making that
clearer.
Daniel Armak
On Tue, Oct 14, 2014 at 5:46 PM, Richard Rodseth rrods...@gmail.com wrote:
I think he's considering Play even for pure REST, because he can use it
from Java, and Akka-HTTP is not ready.
On Tue
Alternatively, if what you want is really to produce the input elements
(returning a Flow[T]) and only add a side-effecting operation, you can
implement it using `map`.
Daniel Armak
On Thu, Jul 24, 2014 at 11:35 AM, Akka Team akka.offic...@gmail.com wrote:
Hi Eric,
There is a foreach
Er, just to point out the obvious mistake in my previous email, it should
be:
Future.sequence(futures map (toTry(_))) onComplete { ... }
Daniel Armak
On Mon, Jul 21, 2014 at 9:21 PM, Greg Flanagan ventis...@gmail.com wrote:
nice, that did the trick. thanks!
On Monday, July 21, 2014 10:52
a `Terminated` message saying your actor died, it didn't
handle that the message and so died with a DeathPactException.
Again, it's possible I'm misunderstanding your case if it's not in fact
similar to the ones discussed at that ticket, but it looks the same as them
to me.
HTH,
Daniel Armak
On Mon
Isn't that what .view.slice does?
Daniel Armak
On Thu, Jun 5, 2014 at 4:34 PM, √iktor Ҡlang viktor.kl...@gmail.com wrote:
Hi,
This sounds plausible to me:
Create an interface that wraps a section of the float array and pass an
instance of that section into the actor when it is created
If they only need readonly access, then why does it matter if the views are
overlapping?
Daniel Armak
On Thu, Jun 5, 2014 at 8:01 PM, Marco Luca Sbodio marco.sbo...@gmail.com
wrote:
Hi,
thank you for your suggestion, but I think I this is not applicable to my
case for two reasons:
- I
compete for CPU, but maybe I was
wrong? Alternatively, would it make sense to use ExecutionContext.global as
the ActorSystem dispatcher's underlying executor?
I'm using akka 2.2.3 with scala 2.10.4.
Thanks,
Daniel Armak
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http
benchmarking, I just haven't had time yet.
And I thought to ask meanwhile if there were any known pitfalls, or large
differences between the two ECs' default configurations?
Thanks,
Daniel Armak
On Wed, May 21, 2014 at 9:59 PM, √iktor Ҡlang viktor.kl...@gmail.comwrote:
Hi Daniel,
Make sure you
I finally created a ticket here, if anyone wants to track this. Let the RS
committers decide.
https://github.com/reactive-streams/reactive-streams/issues/47
On Thu, Apr 24, 2014 at 10:26 PM, Daniel Armak danar...@gmail.com wrote:
Hi Patrik,
I will do so when I have time to write up my case
enough to be part of the API . (As
an optional, but standardized, extra interface a Producer/Consumer can
implement.)
Thanks,
Daniel Armak
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search the archives: https
an HttpResponsePart producer, how do I know what size ByteStrings to send
to the consumer that ships these out to the network?
Daniel
On Mon, Apr 21, 2014 at 2:50 PM, Patrik Nordwall
patrik.nordw...@gmail.comwrote:
20 apr 2014 kl. 00:32 skrev Daniel Armak danar...@gmail.com:
Hi,
How would I use reactive
it will be left to each implementation to introduce its own patterns.
Daniel Armak
--
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
Cast does seem to have the potential for confusion. How about a company
of actors, or maybe troupe?
On Tue, Apr 15, 2014 at 11:43 PM, Justin du coeur jduco...@gmail.comwrote:
On Tue, Apr 15, 2014 at 4:16 PM, √iktor Ҡlang viktor.kl...@gmail.comwrote:
A cast of actors?
Heh. Aside from the
Would that include the new reactive streams?
On Tue, Apr 8, 2014 at 9:25 PM, √iktor Ҡlang viktor.kl...@gmail.com wrote:
Hi Daniel,
On Tue, Apr 8, 2014 at 8:10 PM, Daniel Armak danar...@gmail.com wrote:
On Tue, Apr 8, 2014 at 5:22 PM, Roland Kuhn goo...@rkuhn.info wrote:
The release
On Fri, Mar 14, 2014 at 12:16 AM, Roland Kuhn goo...@rkuhn.info wrote:
The idea with actors is that they shall remain responsive whenever
possible. Another way to look at it is that the internal queue (or stash)
should be limited, and when it overflows you might want to send a negative
reply
On Thu, Mar 13, 2014 at 11:27 PM, Roland Kuhn goo...@rkuhn.info wrote:
Futures very cleanly model local dataflow. Actors very cleanly model
distribution and concurrency. My guess is that if you try to create an
abstraction in-between then it will have the disadvantages of both and the
that cannot be guaranteed if
there are concurrent senders.
-Endre
On Sat, Mar 8, 2014 at 8:08 PM, Daniel Armak danar...@gmail.com wrote:
My intent was definitely to throw away type safety. In my example you can
wrap any ActorRef using any trait, and you can extract and use the raw
ActorRef
dealing with.
But I'm taking your advice to heart. I'll try to use pure actors until I
have more of a sense of how problematic various issues are.
Thanks!
Daniel Armak
On Sat, Mar 8, 2014 at 8:59 PM, Derek Wyatt de...@derekwyatt.org wrote:
On 8 March 2014 13:31, Daniel Armak danar
how
do mature actor-based projects handle these issues? How can I have the
benefits of both actors and static typing?
TIA for any insight.
Daniel Armak
--
Read the docs: http://akka.io/docs/
Check the FAQ:
http://doc.akka.io/docs/akka/current/additional/faq.html
Search
make it easier to migrate to RS in the future.
Thanks!
Daniel Armak
--
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
27 matches
Mail list logo
