3

I am using flask framework to interface a text-to-speech system to web. Basically website takes input via textbox and returns a audio file. Once text is entered into text box and a button is pressed below call-back will be invoked. 

def task_text2speech():

    # call to my text to speech system 
    # respond to client

In above above function step "# call to my text to speech system" will take around 30-100 seconds. During this time client browser will not have any response. I want to overcome this by starting a thread instead of blocking task_text2speech in task_text2speech and once thread is done with speech synthesis respond to client.

For me implementing threading is not a issue, but I am not aware of flask handlers required to respond to client in above scenario. Any docs or example implementation are appreciated.

BenMorel
  • 34,448
  • 50
  • 182
  • 322
U-571
  • 519
  • 2
  • 7
  • 23

1 Answers1

2

A simple, low-tech way you could implement this is by returning a response to the client that indicates that the server is processing the request, and in parallel to that you start your thread to do the work. You will assign a unique ID to each worker thread.

The response page that shows the "processing" message will have an auto-redirect that kicks in after, say, 5 seconds. The redirect will be to a new Flask route that takes the worker thread ID. The view function associated with this route checks the state of the worker thread, and if that thread is still at work it responds with the same "processing" page, so that the client will redirect again in another 5 secs.

When the redirect handler from the processing page finds that the worker thread finished, it can redirect to a new page that offers the generated audio file for download.

I hope this helps.

Miguel Grinberg
  • 65,299
  • 14
  • 133
  • 152
  • Thanks a lot for the answer. It solves my requirements. Since I am new to web dev and flask few dumb questions. 1) how to implement auto-redirection in the response page. 2) how to embed a ID in response page and get it back via auto-redirected url. – U-571 Jun 30 '13 at 09:30
  • 1) add a [meta refresh](http://en.wikipedia.org/wiki/Meta_refresh) in the head section of your page. 2) the refresh URL can have an ID that uniquely identifies the worker thread, for example: http://example.com/progress/?worker=123. You will of course need to assign unique IDs to all your worker threads. – Miguel Grinberg Jun 30 '13 at 21:37
  • You can use [Server-Sent Events](http://stackoverflow.com/a/12236019/238472) to avoid client side timer. – Answeror Sep 12 '13 at 02:58