Allow for a IFn to be passed back as the body object #3
Hi Eric,
Changing the Ring spec in this way is non-trivial, and not something we would do casually. This change in particular is tricky because it deals with async responses, which are not something Ring supports in a first-class way right now.
The best way to move forward with being able to solve your problem with a mainline Ring distribution would be to write to the Ring mailing list (per the Ring Readme). If you could describe the problem that you wanted to solve, demonstrate with some code samples, and describe how you ended up solving it with your patch, that would be a good start for async discussion.
Thanks,
- Mark
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I needed to be able to safely stream data out via a ring http server. The way I came up with was by having the rendering logic open the output stream and then pass it back to a callback function which does the actual writing. I have this running on our machines and it works, but it would be nice if it were incorporated into the actual system :).
Let me know if you need me to do anything to be able to get this merged in.