Re: [akka-user] Distributing lots of large messages to a cluster on startup issue.

As Roland said, it is probably best to use some kind of side channel for large blobs. One thing you could do that is a bit out of the left field is to run ipfs on each cluster node. Then you could save the 10MB data block in ipfs and just link to the data from the message. The

Re: [akka-user] [akka-http-2.0.2] multipart and fields and fileupload problem

Hi Marek, This seems to happen whenever the request entity is non-strict. I suppose you should be able to workaround this issue using entity.toStrict. But of course I think this should work out of the box. If somebody wants to take a deeper look at this, here is a standalone reproducer:

Re: [akka-user] [akka-http-2.0.2] multipart and fields and fileupload problem

} Directive[Unit](toStrict0) } On Mon, Jan 18, 2016 at 2:38 PM, Roland Kuhn <goo...@rkuhn.info> wrote: > Thanks a lot for the gist, would you mind filing a ticket? > > Regards, > > Roland > > 18 jan 2016 kl. 14:09 skrev Rüdiger Klaehn <rkla...@gmail.com>: >

Re: [akka-user] [akka-http-2.0.2] multipart and fields and fileupload problem

OK, done https://github.com/akka/akka/issues/19506 I guess the reason I did not find a toStrict directive is that you don't want to encourage people to do this, since it will of course blow up with an OOME if you do a really large POST request... :-) On Mon, Jan 18, 2016 at 2:52 PM, Marek

Re: [akka-user] Dependency problem when updating to akka-http 2.0.1

Hi Roland, I did a sbt clean, and my colleague even deleted the ivy cache. We also don't know the offending code, since we do not intentionally use anything out of javadsl, such as akka.http.javadsl.model.MediaType. So I am a bit confused. The migration guide does not say anything about

Re: [akka-user] [akka-http] problem with multiple client requests using singleRequest

OK, great. Having done some pretty complex things with the server side API, I was surprised to run into issues on the client side so quickly. I am using akka-http in production (for a small, non mission-critical tool). Should I upgrade to 2.0-M2 or stay with 1.0 and somehow work around the bug?

[akka-user] FTP library

Hi all, I will have to do some FTP uploads from within an akka-based application. My current idea is just to go with apache-commons FTPClient and put the actor on a separate dispatcher to avoid issues with the inevitable blocking calls. This will definitely work and also not cause any issues,

Re: [akka-user] Efficient - transmit only once - broadcast?

to understand how it works On 03/11/15 13:42, Rüdiger Klaehn wrote: > This might not be very nice, but you could pre-serialize your large > object to a akka.util.ByteString. Serialization of an > akka.util.ByteString should be much cheaper than serializing a large. > complex data str

Re: [akka-user] Efficient - transmit only once - broadcast?

This might not be very nice, but you could pre-serialize your large object to a akka.util.ByteString. Serialization of an akka.util.ByteString should be much cheaper than serializing a large. complex data structure. I am assuming that the serialization overhead is what you want to avoid. On Mon,

Re: [akka-user] Http client and chunked encoding

increasing the chunk size? On Tue, Apr 7, 2015 at 11:35 PM, Rüdiger Klaehn rkla...@gmail.com wrote: Thanks a lot. Seems quite obvious now that you explained it. On Tue, Apr 7, 2015 at 12:25 PM, Akka Team akka.offic...@gmail.com wrote: Hi Rüdiger, You are waiting on the finishFuture

Re: [akka-user] Http client and chunked encoding

Thanks a lot. Seems quite obvious now that you explained it. On Tue, Apr 7, 2015 at 12:25 PM, Akka Team akka.offic...@gmail.com wrote: Hi Rüdiger, You are waiting on the finishFuture of the foreach, but not waiting on the internal stream you materialize inside foreach. The finishFuture will

Re: [akka-user] Re: akka-http and closing connections from the client side

Here is a gist of a small file server that uses chunked encoding. You should be able to see the backpressure work with this. https://gist.github.com/rklaehn/3f26c3f80e5870831f52#file-file-server-example If you run it, it opens a server on localhost, port 8080, that serves all files on your

[akka-user] Akka-http: how to deal with incorrect http headers

Hi all, While playing around with akka-http, I wrote a minimal http proxy server: https://gist.github.com/rklaehn/3aa3215046df2c0a7795 To test it, I configured a browser with this as proxy and browsed some popular news web pages that load a zillion things from ad servers, trackers and the like.

Re: [akka-user] Re: Akka-http: how to deal with incorrect http headers

I have looked at the reference.conf of akka-http-core-experimental (1.0-M2) and found the following settings that should solve some of these problems. But adding the configuration below as an application.conf does not seem to make a difference WRT. parsing of Uris. I still get a 400 Bad Request

Re: [akka-user] akka-http (experimental) file server

Hi Allan, I updated the gist https://gist.github.com/rklaehn/3f26c3f80e5870831f52 to work with 1.0-M2. However, I am not sure if what I do is idiomatic. It seems to work though. On Mon, Dec 22, 2014 at 9:03 PM, Allan Brighton allane...@gmail.com wrote: Is there an example http file server and

Re: [akka-user] Akka Streams - Chunked Encoding

I am not completely sure, but the dead letters are probably nothing to worry about. I had a similar experience when I played around with it a few weeks ago. See this thread: https://groups.google.com/d/topic/akka-user/4ybCq7mEp4g/discussion On Wed, Nov 26, 2014 at 11:52 PM, Paul Cleary

Re: [akka-user] Re: Basic HTTP client with Akka HTTP

Something like a akka-http based curl equivalent would be a great asset for testing, and also a good example. However, I am not sure how much the syntax will change from now to 1.0. If you want to play with it, one capability I would like to see is client-side bandwidth limiting (like the

Re: [akka-user] akka-http (experimental) file server

On Thu, Nov 20, 2014 at 3:31 PM, Allan Brighton allane...@gmail.com wrote: Thanks for the http server example. It works fine. Do you also have a matching example for the client side? I found akka.http.TestClient, which is a start, but does not give any hints about reading the data from the

Re: [akka-user] [akka-http] Graceful Shutdown

There is a ticket for this: https://github.com/akka/akka/issues/15945 What I am currently doing in my test code is to store the Http.ServerBinding (which now implements AutoCloseable) in the actor and call close on it if I want to get rid of the server binding. I am not sure if this is the

[akka-user] akka-http and closing connections from the client side

Hi all, I am doing some testing with akka-http and chunked encoding. I want to investigate the backpressure behavior, so I am using curl with --limit-rate 1k on the client side. I should I see backpressure when using akka-http to send a HttpEntity.Chunked, right? One thing I noticed is that all

Re: [akka-user] akka-http and closing connections from the client side

On Tue, Oct 28, 2014 at 10:40 AM, Akka Team akka.offic...@gmail.com wrote: Hi Rüdiger, I am doing some testing with akka-http and chunked encoding. I want to investigate the backpressure behavior, so I am using curl with --limit-rate 1k on the client side. I should I see backpressure when

[akka-user] akka.stream.scaladsl.Flow and flatMap

Hi All, I just took a quick look at the new reactive streams API and in particular the scala DSL at http://doc.akka.io/api/akka-stream-experimental/0.2/index.html#akka.stream.scaladsl.Flow. Looks pretty good so far. I especially like that this is supposed to evolve into a standard for the entire

Re: [akka-user] Distributed transactions in Akka

On Thu, Mar 13, 2014 at 9:38 AM, Roger Alsing rogerals...@gmail.com wrote: Should we stop thinking about transactions as something binary and instant, that either succeeds or fails here and now? I am only lurking. But I would argue that the notion of something happening in multiple places at