This sounds like a bug, please open a ticket about this and thanks for
noticing! If you want to follow up with a PR that would be even more awesome :-)
Regards,
Roland
Sent from my iPhone
> On 07 Jan 2016, at 16:36, Chris Baxter wrote:
>
> I was looking at the Akka Http code recently, speci
I've just realized that I didn't close input stream after Files.copy.
After fixing this timeouts still happen but not every time.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>
Hi,
In the application that I am working on I need to pass content of the uploaded
via HTTP files to Java library that accepts InputStreams. I am trying to use
new StreamConvertes.asInputStream method from akka-http 2.0.1 (akka 2.3.11)
However the server always responds with timeouts. I wonder
Roland, your thoughtfulness exceeds my expectations. I was hoping there was
something already written that I was just failing to find. I know there's a
bunch of stuff to do and explaining the rational on everything is not the
highest priority.
Tim
> On Jan 7, 2016, at 15:12, Roland Kuhn wrote
Hi Tim,
This has not been forgotten, but I'm on vacation now, will reply next week.
Regards,
Roland
Sent from my iPhone
> On 04 Jan 2016, at 06:50, Tim Harper wrote:
>
> A big reason why groupBy, splitWhen (and other split* friends) were useful
> was the ability to apply different behavior
It is not even related to "how many nodes start at once". You can start 100
nodes at once with 1 or 100 seed nodes.
I agree that 3 is a good number. 24 should also not be a problem.
/Patrik
tors 7 jan. 2016 kl. 18:24 skrev Konrad Malawski <
konrad.malaw...@typesafe.com>:
> Konrad, thanks for the
Konrad, thanks for the quick reply. Our nodes are similar (receive same
traffic on same hardware). We have frontend and backend node roles (10 FE, 16
BE). Does 4 nodes (2 from each role) sound reasonable?
Seed nodes are just "the nodes to which a new node talks to in order to join
the cluste
hi hakkers,
i'm working *JAVA* akka-http based app.
i was planning to create a generic handler that handles all common stuff
and only exposes a method for custom logic implementation.
my problem is that handlers that will derive from it in the future will use
different types of inputs. some wil
This is probably more of a generic scala question, but I figured the very
best scala developers are clearly found in the akka mailing list, right? :)
I would like my verifyScopes directive to magically find my parseScopes
function without me having to explicitly pass it as a parameter. If I do
ok, i found a solution
response.withEntity( MediaTypes.APPLICATION_JSON.toContentType(), data)
does the job
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the arc
10 matches
Mail list logo
