My understanding is that it's currently an external dependency, not distributed with Java SE, but eventually would become part of the SE in a future JVM release.
I would be kinda against to use this client as an replacement for our implementation, it will be harder to reason about resources like that, fs2-http is meant to implement the whole stack. Also, I am quite sure that this dependency requires java 9, and at that point it can be implemented easy in our current stack
Or is the whole http implementation written from scratch?
Please, do not commit this
For the love of all 8 billion humans on this earth
As a fs2 newbie, I'm having some trouble implementing an integration test that involves WebSocket, fs2 and fs2-http. I've implemented a service that receives events (
submitToQueueViaWebSocket below) and publishes those events to subscribers via WebSocket. I'm trying to create an integration test for this.
The code looks something like this:
def createWebSocketStream: Stream[F, Unit] = ???
def submitToQueueViaWebSocket: F[Unit] = ???
def createShareAndQueue: F[String] = ???
def wscon(h: String, id: String) = for {
q <- Stream.eval(Queue.unbounded[F, String])
r <- Stream(q.dequeue.concurrently(createWebSocketStream))
} yield r
(for {
id <- Stream.eval(createShareAndQueue)
res0 <- wscon("localhost", id)
_ <- Stream.eval(submitToQueueViaWebSocket)
} yield res0).take(1).compile.toListsubmitToQueueViaWebSocket submits data that will end up in the queue which results in the q.dequeue stream emitting an item, which in turn results in submitToQueueViaWebSocket getting invoked turning it into an endless recursion. This seems to be ok as long as I only take a fixed amount of items from the stream. I've also tried changing wscon to return a Stream[F, Stream[F, String]], but in that case the program doesn't terminate. Another approach I've tried is change wscon to return a Stream[F, Stream[F, String] instead of a Stream[F, String]. This would help with the recursion, but for some reason I the initial item from the queue doesn't seems to get published via WS. The latter somehow feels like the better approach, but I can't figure out why the initial item doesn't get published.Any thoughts from the more experienced fs2-http practitioners?
Use scalajs-dom with fs2
But as of now there's no fs2-based HTTP library that covers 2.13 and ScalaJS
As of now the Travis build is broken too
As I understand
master is not used at all
Is there a reason for that?
Feedback on fs2 v2 upgrade PR #41 would be greatly appreciated.
What would be the best way to determine default blocking context thread pool sizes? Just a fixed number or base it on execution environment properties?
What would be the best way to determine default blocking context thread pool sizes? Just a fixed number or base it on execution environment properties?
Hello team! I'm using WebSocket client, and have a question how I can check when WebSocket connection is closed? From documentation I have read:
* If this is established successfully, then this consults `pipe` to receive/sent any frames
* From/To server. Once the connection finishes, this will emit once None.But I can't reproduce this behavior. I shut down the server, and never receive any messages.
Is #37 not merged because its not finished?
I really want to get fs2 v2, scala 2.13, and scalajs support on this library because it's basically the best for real streaming clients
And my project depends on fs2 v2 and scala 2.13 and fs2-http is also the only thing holding it back from scalajs support as well
is what gives you features. It works now. @AdamChlupacek when you will address the review so we can merge and make release?