> On 25 May 2016, at 00:33, Jack Daniels wrote:
>
> Could you please explain meaning of `maximumBurst` parameter with example?
If you throttle to a certain rate, `maximumBurst` defines what should happen if
fewer elements have arrived from upstream for some time (your bucket contains
some toke
Try to use a java.util.List as the value for the contact points
configuration. One address in each element of the list. I'm not sure if it
works.
/Patrik
tis 24 maj 2016 kl. 23:35 skrev Yan Pei :
> I am trying to dynamically set up value for
> cassandra-journal.contact-points.
>
> If I am using C
Has anyone used FST Serialization[1] with their Akka messages? If so, how
did it work out? I am debating using this or Kryo for serialization and FST
seems to be faster and more "drop-in" compliant so i was curious if anyone
had tried it. If you have tried Kryo before I would be interested in yo
Could you please explain meaning of `maximumBurst` parameter with example?
It's unclear to me from ScalaDoc.
On Wednesday, May 25, 2016 at 1:17:45 AM UTC+3, Konrad Malawski wrote:
>
> Throttle a Flow?
> Sorry, I did not dive deep into your code, as perhaps there's no need to,
> because:
>
>
> ht
Throttle a Flow?
Sorry, I did not dive deep into your code, as perhaps there's no need to,
because:
http://doc.akka.io/docs/akka/2.4.6/scala/stream/stages-overview.html#throttle
and
throttle on http://doc.akka.io/api/akka/2.4.6/#akka.stream.scaladsl.FlowOps
--
Konrad `ktoso` Malawski
Akka @ Lig
Hi guys!
How do you throttle Flow in the latest Akka (2.4.6) ? I'd like to throttle
Http client flow to limit number of requests to 3 requests per second. I
found following example online but it's for old Akka and akka-streams ApI
changed so much that I can't figure out how to rewrite it.
de
I am trying to dynamically set up value for
cassandra-journal.contact-points.
If I am using ConfigFactory.parseString(). It works well.
String name = "cassandra-journal.contact-points=";
String contactPoints = name + "[ipaddress, ipaddres]";
Config overrides = ConfigFactory.parseString(contactPoi
Enable it:
# Enables/disables the addition of a `Raw-Request-URI` header holding the
# original raw request URI as the client has sent it.
akka.http.server.raw-request-uri-header = off
and then you'll get a magic header which contains the raw URI in each request.
I already wondered why they are no
On 05/24/2016 09:02 PM, Konrad Malawski wrote:
Enable it:
# Enables/disables the addition of a `Raw-Request-URI` header holding the
# original raw request URI as the client has sent it.
akka.http.server.raw-request-uri-header = off
and then you'll get a magic header which contains the raw URI
well, no reason..., I just did not follow your comment "... have the
account id as the persistenceId."
On Tuesday, May 24, 2016 at 8:35:21 PM UTC+3, code@gmail.com wrote:
>
> Hi all,
>
> I think the most convenient way consuming of persisted events is using
> eventsByTag, so I have a dile
Without knowledge of your domain, the tag would be something like
"Customer" and the ID would be customer_456 (or a UUID)
any reason you like to attach the account_123 upfront ? Looks like some
kind of relation between account and customer.
On Tuesday, May 24, 2016 at 8:37:22 PM UTC+2, code...
Enable it:
# Enables/disables the addition of a `Raw-Request-URI` header holding the
# original raw request URI as the client has sent it.
akka.http.server.raw-request-uri-header = off
and then you'll get a magic header which contains the raw URI in each request.
Happy hakking!
--
Konrad `ktoso
yep multiple tags could be a good option, as it can give me more freedom in
the future if I decide to change replay logic.
Olger, regarding your solution, for example if we take customer aggregate
root, tag should be "customer" and persistenceId should be something like
"account_123_customer_45
I'd suggest to use tags per aggregate root and have the account id as the
persistenceId.
when you use cluster sharding, that gives a great option to 'instantiate' a
specific instance of the aggregate root and for the query side you use the
tags.. works quite well in practice.
kind regards,
Hi,
I am using both, as in cassandra plugin you can have 3 tags for each
events. While the tag at position 2 and 3 should be known in advance, the
first tag is free. So I am using to tag the event with a particular Id that
make sense to my domain.
To be fair in the first tag I also put some bounde
Hi all,
I think the most convenient way consuming of persisted events is using
eventsByTag, so I have a dilemma of tagging events, for example I see two
options:
1. by bounded context (like inventory, customer etc)
2. by account id
In the second case you can expect a lot of consumers, let's s
Is it possible to get the encoded HTTP request that arrives at the server
(as it is represented in the raw HTTP request)?
akka.http.scaladsl.model.HttpRequest and
akka.http.scaladsl.server.RequestContext seem to contain only the decoded
URI. Can I have access to the raw HTTP request if nothing
For anyone wondering - the answer was to use the following:
>
> pathPrefix(
> PathMatchers
> .segment(PATH_V1)
> .slash(PATH_ORDERS)
> .slash(PATH_PARAM_UUID),
> orderId -> pathPrefix(
> PathMatchers
> .segment(PATH_MAJOR_VERSION)
> .slash(PATH_PARAM_MAJOR_VERSION)
> .slash(PATH_MINOR_VERS
PathDirectives has path(PathMatcher1... and path(PathMatcher2... but no
path(PathMatcher3 or onwards.
I get that there has to be a limit at some point for people who want 52
variables in their URLs - but Is there some alternative way I am supposed
to write the equivalent of this code which matches
19 matches
Mail list logo
