I am trying to create a pair of Flow graphs that support some conversion
between ByteString and T.
The inbound ByteString messages are chunked by a fixed size (e.g. 8K) thus
boundaries land at arbitrary points in the data being processed.
As such, the in to out message processing is not 1:1, but
Vert.x is just another reactive framework, I found it easier to use than
Akka HTTP for Java that's all, and I think (at least today) it is faster.
I cannot really recommend you one or the other just state what I know, the
decision is still yours.
I know Akka team works very hard on improving
Hi Eduardo,
threads created by other libraries are not managed by Akka, you will have to
shut down that external DB interface yourself. The best place to do this would
be in the actor’s postStop() hook (I mean that actor which also creates and
uses that DB).
Regards,
Roland
> 14 mar 2016
Yeah that's the one though please note that it can be separately configured for
server (akka.http.[server].parsing.max-content-length),
full docs on it here:
http://doc.akka.io/docs/akka/2.4.2/scala/http/common/http-model.html#limiting-message-entity-length
--
Cheers,
Konrad 'ktoso’ Malawski
thanks!
I assume it is akka.http.parsing.max-content-length config
W dniu piątek, 11 marca 2016 15:44:15 UTC+1 użytkownik Akka Team napisał:
>
> Hi Marek,
>
> It is not the header that is null, the exception is thrown because there
> was a body that was to big. The reason you get null in the
Hi Roland.
Thanks for your answer.
Sure, the problem was that I was not aware about that threads. I'm afraid
that I have to shutdown such threads at system shutdown because the library
shares threads among several actor instances. Anyway, problem solved!
Thanks again for your time very helpful
Hi Guido,
thank you for the shared info.
We are planing to use Google's Protocol Buffer
(https://developers.google.com/protocol-buffers/) instead of JSON.
You recommend using Vort.x with Netty implementation instead of Akka HTTP
for now?
Br,
Alan
Dana srijeda, 9. ožujka 2016. u 11:11:43
Hi
I need sample codes using Akka Actor and apache camel,
we are using thorn actor c++ library, i want get same functionality in
SCALA but not got thorn :: ENDPoint equalient class in both the packages
in Akka Actor and apache camel
Thanks in advance
Sudhakar
--
>> Read
Hi,
i need to create a UDP server binding to one port.
Multiple clients (devices) will "connect" to this port and each device
"connection" has to be handled by its own actor (DeviceActor). DeviceActor
would be responsible for handling received messages, replaying to received
messages
So if you look at the example in the
docs:
http://doc.akka.io/docs/akka/2.4.2/scala/http/client-side/request-level.html#Using_the_Future-Based_API_in_Actors
That works fine. Except it's incomplete since it's obviously a single-use
Actor (the request is fired off in preStart) and it doesn't
As a side node: self is already defined as context.self in Actor, you can
use that directly.
Le lun. 14 mars 2016 à 18:36, Sam Smoot a écrit :
> So if you look at the example in the docs:
>
Could it be that since you define an implicit Materializer in your actor
which is tied to the implicit ActorRefFactory (which would be context
inside the actor), it is the one used for singleRequest which requires an
implicit Materializer? Can you try defining your Materializer as
Hello All,
we have a small service that implements a REST API, and we use Akka to
enable concurrency, for structure and readibility of our code. All works
fine, except I'm struggling now with our security integration. We're using
Spring as our 'container' framework and Spring Security to
That fixed it! I can't thank you enough!
On Monday, March 14, 2016 at 5:43:05 PM UTC-5, Samuel Tardieu wrote:
>
> Could it be that since you define an implicit Materializer in your actor
> which is tied to the implicit ActorRefFactory (which would be context
> inside the actor), it is the one
Ah. I didn't realize self was a val. I always assumed it was just a
delegating method to context.self. Thanks for the tip.
For posterity: I was trying to provide a local val the closure I was using
for my Future callback could capture so that if the underlying ActorRef
returned by context.self
15 matches
Mail list logo