[Haskell-cafe] Lifetime control of webserver
maydwell at gmail.com
Fri Jul 13 02:54:41 UTC 2018
Yes that's what I had in mind.
You can do some fun things with Control.Concurrent.Chan as well if you need
special sequencing, or limits on requests served or callbacks into the main
On Fri, Jul 13, 2018 at 12:32 PM ☂Josh Chia (謝任中) <joshchia at gmail.com>
> Do you mean something like calling the scotty function in a server thread
> and then killing the server thread when I want to stop serving? If proper
> cleanup happens when I kill the thread, this should work for me.
> On Fri, Jul 13, 2018 at 10:01 AM Lyndon Maydwell <maydwell at gmail.com>
>> Not sure if I'm missing something, but is there any reason why you
>> couldn't spin up the server in a thread then kill it when required?
>> - Lyndon
>> On Fri, Jul 13, 2018 at 11:51 AM ☂Josh Chia (謝任中) <joshchia at gmail.com>
>>> My application is not a webserver but needs to run a webserver for part
>>> but not all of its lifetime. Particularly, there's a part that does some
>>> complex computation and I want a webserver to expose its internal
>>> state/progress through HTTP.
>>> It seems that the typical and expected way to use a webserver is to
>>> designate the entire app itself as a webserver, so that functions like the
>>> following are basically infinite loops that serve HTTP:
>>> Can I run a webserver with explicit control of its lifetime?
>>> Particularly, I want to be able to kill it without killing the app or
>>> explicitly serve one request at a time. I'm not restricted to scotty or
>>> Haskell-Cafe mailing list
>>> To (un)subscribe, modify options or view archives go to:
>>> Only members subscribed via the mailman list are allowed to post.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haskell-Cafe