Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scotty vs. WAI 3.0 continuation-passing style #260

Closed
florpe opened this issue Jan 19, 2020 · 3 comments
Closed

Scotty vs. WAI 3.0 continuation-passing style #260

florpe opened this issue Jan 19, 2020 · 3 comments
Labels

Comments

@florpe
Copy link

florpe commented Jan 19, 2020

I've been trying unsuccessfully to write a function ScottyM () -> ActionM () (or WAI.Application -> ActionM (), really) in order to use Scotty applications as plugins. As far as I can tell the main difficulty with this is that Scotty still uses the pre-WAI 3.0 style of application internally. Is there a technical reason for this, or would it be worthwhile to try and migrate Scotty to CPS?

@chessai
Copy link
Contributor

chessai commented May 16, 2020

Investigating this might be worthwhile. The design of scotty is pretty old, and I have gripes with a lot of it.

@ocramz ocramz added the R&D label Sep 23, 2023
@jfraudeau
Copy link
Contributor

Not sure how it relates to WAI 3.0 but it looks like the use case was implemented in #233

@florpe If it is still relevant to you can you confirm ?

@ocramz
Copy link
Collaborator

ocramz commented Sep 25, 2023

Yep, now we have nested as @jfraudeau pointed out. Thanks!

@ocramz ocramz closed this as completed Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants