Thanks, Bryan, for your response. To give a bit more context - my directory application uses Flask for routing and embeds the Bokeh server. My initial attempt had a Select2 Select widget declared in a jinja2 template. By routing to (say) url1, I was able to run Python code to generate the 10K entries I needed. The resulting JSON was supplied to the ‘Options’ tag of the Select. Upon rendering the the template, I was able to choose one of the options in a reasonable time. Next, I wanted to use the selection to constrain further data and present a set of tables. For this purpose, I wrote a java script snippet to respond to the change event of the Select widget. In the success clause, I routed to (say) url2 with parameters from the Select. This second url routed to an embedded Bokeh server document. The resulting script was embedded into another jinja2 template, which was rendered. I did not see the expected layout of the second template. I do know from the messages (and Python print statements) that the request was successfully routed to the embedded Bokeh server and a script was returned.
This set me to think about a pure Bokeh solution and the questions I have asked on this forum.
Perhaps, the following is an architectural question and the information I gave is insufficient to answer it. However, in the interest of starting the dialogue to solve it, here is the question -
Given the above and the need to do a ‘contains’ search on a large data set, what is the best solution?
If this is not the best place to ask a question of this type, please do guide me to the appropriate forum/protocol.