Hi guys,
Strangely I couldn't post this meesage to akka-user, google groups was
failing.
I have few questions
1) According to
https://docs.google.com/document/u/0/d/18W9-fKs55wiFNjXL9q50PYOnR7-nnsImzJqHOPPbM4E/pub
ETA
for Akka 2.4 release is April 2015. I assume it will include akka-streams
Hi,
we're evaluating akka-stream for the usage in a future project of ours. The
IRC client spec (https://tools.ietf.org/html/rfc2812) is somewhat
comparable to what we will need to be able to do in our real project. I'm
struggling with the design of a graph in which the source has to emit
Thank you for your explanation!
I tried to solve the problem by implementing my own mailbox, that
deletes old messages when full (that is my requierement).
As I understand you, this will not work, as the stashing is not using
the mailbox?
But how can I change the stash-capacity behaviour, so
Reading http://doc.akka.io/docs/akka/snapshot/general/addressing.html,
Reusing Actor Paths, I would agree with you:
It may be the right thing to do in very specific circumstances, but make
sure
to confine the handling of this precisely to the actor’s supervisor, because
that is the only actor
Hi,
I've decided to dive into the streams ;) and implemented a client for
etcd[1] using akka http client. It worked really well, and was a lot of fun!
However, I'm missing one final piece that I wasn't able to figure out: The
client offers a watch function that returns a stream of
Hi Roland / List,
I am looking into an addition/mutation to the Persistency layer that allows
storage of an aggregateId (more or less the whole 'tag' idea without being
able to have multiple tags to start out with) with a replay (for the view)
based on that aggregateId. (bit like the DDD
I think I've moved one step closer: I think I know how to weld a flow
breaker into my graph:
def watch(key: String, waitIndex: Option[Int] = None, recursive:
Option[Boolean] = None, quorum: Option[Boolean] = None):
Source[EtcdResponse, Cancellable] = {
case class WatchRequest(key:
W dniu piątek, 24 kwietnia 2015 14:24:35 UTC+2 użytkownik drewhk napisał:
The question now remains, how do I fabricate a Graph[FlowShape[T, T],
Cancellable] that will generate an instance of Cancellable on each
materialization connected to a PushPullStage, in such way that cancel()
would
Hi Rafal
On Fri, Apr 24, 2015 at 2:21 PM, Rafał Krzewski rafal.krzew...@gmail.com
wrote:
I think I've moved one step closer: I think I know how to weld a flow
breaker into my graph:
def watch(key: String, waitIndex: Option[Int] = None, recursive:
Option[Boolean] = None, quorum:
Hi
What is the status for akka-http TLS support, Is there an ETA?
I'm developing using akka-http and my integrations to 3rd party services
(SendGrid) must go over https. I looked at the source code but could not
find anything for TLS support in akka-http. Any workarounds that would be
Is there any documentation about the new websocket api?
On Friday, 24 April 2015 23:04:37 UTC+2, Magnus Andersson wrote:
By the way
These packages seems to be missing:
com.typesafe.akka:akka-http-experimental_2.11:1.0-RC1
com.typesafe.akka:akka-http-testkit-experimental_2.11:1.0-RC1
What is the scope of .withAttributes()? Does it only apply to the stage
that it is called on, or every stage up to that point? For Example
Sink.empty.transform(() = ...).transform(() =
...).withAttributes(ActorOperationAttributes.dispatcher(test-dispatcher))
Are all the transformation stages
Roland tweeted yesterday:
Yesterday the #jaxcon https://twitter.com/hashtag/jaxcon?src=hash award,
today merged HTTP client (@sirthias https://twitter.com/sirthias) and
WebSockets (@virtualvoid https://twitter.com/virtualvoid) and TLS
support—can tomorrow be even better?
On Fri, Apr 24, 2015
Well,
I found that the sequence numbers are actually generated on a per
persistent actor instance basis.
So that makes replay for a single aggregateId based with limits on the
sequence numbers a bit of an intresting challenge
Still interested in your opinions as that will have impact on the
Haha, good answer. I missed that tweet!
Both TLS and WebSockets, that is great news more than I would have hoped
for. Now I'm very eager for a new Milestone release.
/Magnus
2015-04-24 16:45 GMT+02:00 Richard Rodseth rrods...@gmail.com:
Roland tweeted yesterday:
Yesterday the #jaxcon
On Tue, Apr 21, 2015 at 1:25 PM, Anders Båtstrand ander...@gmail.com
wrote:
Have you tried running the master actor and the workers with different
dispatchers?
http://doc.akka.io/docs/akka/snapshot/scala/dispatchers.html
You could, just for test, assign a PinnedDispatcher to the master
On Mon, Apr 20, 2015 at 10:38 PM, Nweike Onwuyali nweikeonwuy...@gmail.com
wrote:
Hi,
Thanks for your response. I want to query a couchDB using REST. However, i
want to put the business logic of doing so in Actors(Akka) instead of Play
models. The Actors will perform the request and also
Very nice work! Excited to get started.
I was asking about TLS for akka-http just a few hours ago in another
thread. Really hoping you manage to squeeze the high level APIs into 1.0.
In the mean time, are there some examples of SSL+HTTP (HTTPS) for client
connections? I don't mind using
By the way
These packages seems to be missing:
com.typesafe.akka:akka-http-experimental_2.11:1.0-RC1
com.typesafe.akka:akka-http-testkit-experimental_2.11:1.0-RC1
Looked at the Maven repo and RC-1 were not present:
https://repo1.maven.org/maven2/com/typesafe/akka/akka-http-experimental_2.11/
19 matches
Mail list logo
