wai-eventsource integration (turn a wai Application into ActionT) about scotty HOT 7 CLOSED

Any progress on this issue?

from scotty.

Well, now (since #233) you can have nested wai Applications under a Scotty route!

from scotty.

Ah I can implement this. I'm not near a computer right now, but soon. Thanks for reporting!

from scotty.

I think the most promising way to fix this issue is to make ScottyResponse more general:

data ScottyResponse = SR
  { srStatus  :: Status
  , srHeaders :: ResponseHeaders -- ^ additional headers to append to the srResponse
  , srResponse :: Network.Wai.Response
  }

I guess it is possible to keep existing API the same. Do you have some considerations against this changes or any better ideas?

from scotty.

I've been looking at websockets and Scotty and my current solution is to handle websockets outside the Scotty app. It's not elegant but it works.

from scotty.

What's the status on that? I wrote a simple handler to test how that could be done:

sse :: T.Text -> ActionM ()
sse t = do
     setCorsHeader
     setHeader "Content-Type" "text/event-stream"
     setHeader "Cache-Control" "no-cache"
     setHeader "Connection" "keep-alive"
     raw $ encodeUtf8 t

And it works, but drops the connection nevertheless.

from scotty.

What's the status on that? I wrote a simple handler to test how that could be done:

sse :: T.Text -> ActionM ()
sse t = do
     setCorsHeader
     setHeader "Content-Type" "text/event-stream"
     setHeader "Cache-Control" "no-cache"
     setHeader "Connection" "keep-alive"
     raw $ encodeUtf8 t

And it works, but drops the connection nevertheless.

Why does this drop the connection despite having the keep-alive header?

from scotty.