mdedetrich commented on PR #2156:
URL: https://github.com/apache/pekko/pull/2156#issuecomment-3261704960

   > This definitely makes it easier to find.
   > 
   > This does beg the question whether we should move and deprecate all 
methods in 
https://pekko.apache.org/docs/pekko/current/stream/operators/index.html#additional-sink-and-source-converters
 .
   > 
   > The warning there (which is also in your javadoc/scaladoc) is that this 
will use blocking operations. That could be a reason to discourage this API, 
and putting them in the separate `StreamConverters` might be a good way to do 
that. So from that perspective, perhaps having them in `StreamConverters` (and 
thus harder to find) might be a good thing?
   
   I would be against removing these blocking methods, as I have in the past 
used the frequently with other API's that only work with 
`InputStream`/`OutputStream` which is very common in Java land.
   
   There is nothing you can do about these methods being blocking as the 
underlying `InputStream`/`OutputStream` are also blocking, it is what it is. 
There are the annoying gotcha's, i.e. its easy to make deadlocks because actor 
stream materialization cannot be blocking but this is the price we have to pay 
when working with Java API's


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org
For additional commands, e-mail: notifications-h...@pekko.apache.org

Reply via email to