I finally created a ticket here, if anyone wants to track this. Let the RS
committers decide.
https://github.com/reactive-streams/reactive-streams/issues/47
On Thu, Apr 24, 2014 at 10:26 PM, Daniel Armak wrote:
> Hi Patrik,
>
> I will do so when I have time to write up my case (on the RS generi
Hi Patrik,
I will do so when I have time to write up my case (on the RS generic
level), in the next few days.
Thanks!
Daniel
On Wed, Apr 23, 2014 at 12:36 PM, Patrik Nordwall wrote:
>
>
>
> On Tue, Apr 22, 2014 at 8:26 PM, Daniel Armak wrote:
>
>> On Tue, Apr 22, 2014 at 1:42 PM, Patrik Nord
When choosing to use ByteString as the element type you accept the risk of
getting a huge bytestring.
The solution is simple: use a type that restricts the size to what you
want. (Hint: that could be a type that wraps the ByteString but errors out
on too large ones)
On Apr 22, 2014 8:27 PM, "Danie
On Tue, Apr 22, 2014 at 8:26 PM, Daniel Armak wrote:
> On Tue, Apr 22, 2014 at 1:42 PM, Patrik Nordwall <
> patrik.nordw...@gmail.com> wrote:
>
>> Yes, uncompressing processor must be able to buffer and send smaller
>> chunks downstream. If it has a compression ratio of 10:1, and it gets
>> deman
On Tue, Apr 22, 2014 at 1:42 PM, Patrik Nordwall
wrote:
> Yes, uncompressing processor must be able to buffer and send smaller
> chunks downstream. If it has a compression ratio of 10:1, and it gets
> demand from downstream of 1000 chunks it should request 100 chunks from its
> upstream. It can no
On Mon, Apr 21, 2014 at 2:26 PM, Daniel Armak wrote:
> Hi Patrik,
>
> That can be done, but what bothers me is the potential lack of
> standardization. Every programmer will solve this problem all over again
> for each stream they build. Even if particular Reactive Streams
> implementations offer
Hi Patrik,
That can be done, but what bothers me is the potential lack of
standardization. Every programmer will solve this problem all over again
for each stream they build. Even if particular Reactive Streams
implementations offer generic tools, they won't be compatible across
implementations or
> 20 apr 2014 kl. 00:32 skrev Daniel Armak :
>
> Hi,
>
> How would I use reactive streams in general, and/or akka streams in
> particular, to represent a stream of binary data? I'm thinking of all binary
> streams that don't have a natural division into chunks of a fixed (small)
> size; you
Hi,
How would I use reactive streams in general, and/or akka streams in
particular, to represent a stream of binary data? I'm thinking of all
binary streams that don't have a natural division into chunks of a fixed
(small) size; you can divide them into chunks any way you want and all
processors i
