I'll send you what I've done if it works
@srnb_gitlab I have tried it, and sadly it seems its not currently that straight forward, we are using some flags which seem not to be supported in 2.13 anymore. We already have a contributor in protocols trying to get it working for 2.13, I will ask him to make sure that everything other than kafka is working and at that point I will make a snapshot from the branch.
@lJoublanc I've been learning about HTTP/2 and QUIC and I kinda want to make a contribution to fs2-http with them
@AdamChlupacek I see htt4s has support - I wonder how they manage it without the JVM version restriction.
Do not take me 100% on this here, but basically, if you have your own SSL stack then you can do what ever, we however are using the fs2-crypto, which for the ease of things is using the java SSLEngine to provide SSL/TLS, which in java 8 sadly does not support the extension. To which, as I mentioned, I saw somewhere some patches to get the extension support there, but to me it is a bit weird to override the default classes, it makes a mess of the dependencies.
Quick look at http4s they are using this jetty thing as well
And here you go, https://github.com/http4s/blaze/blob/master/examples/src/main/scala/org/http4s/blaze/examples/http2/H2ClientExample.scala from http4s which says that the user has to modify their boot path so that the jetty overried is included
How would you feel about a dependency on the JDK 9 incubator httpclient? Do you think that would work?
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?