<Blacksmoke16Geor>
or if thats not an option, have the request enqueue some message somewhere and let another process handle it. like RabbitMQ, or something
greenbigfrog has quit [Ping timeout: 246 seconds]
straight-shoota has quit [Ping timeout: 260 seconds]
jhass has quit [Ping timeout: 240 seconds]
straight-shoota has joined #crystal-lang
jhass has joined #crystal-lang
hightower3 has joined #crystal-lang
hightower2 has quit [Remote host closed the connection]
greenbigfrog has joined #crystal-lang
hightower3 has quit [Ping timeout: 240 seconds]
<tprepper>
hm, that is a good idea, yeah. the application kind of serves as the service that queues downloads though.
<Blacksmoke16Geor>
<tprepper> "hm, that is a good idea, yeah..." <- wonder what would happen if you just spawn a fiber in the controller action and return a 201 response
<Blacksmoke16Geor>
id think it would work on the download after the response has been returned, so that might be worth exploring as the simplest way
hightower2 has joined #crystal-lang
<tprepper>
that could work, yeah.
alexherbo2 has joined #crystal-lang
Flipez has quit [Quit: Ping timeout (120 seconds)]
Flipez has joined #crystal-lang
debayer948 has joined #crystal-lang
debayer948 is now known as debayer
jmdaemon has joined #crystal-lang
_ht has quit [Quit: _ht]
debayer has quit [Ping timeout: 248 seconds]
alexherbo2 has quit [Remote host closed the connection]