Getting work done while anvil.server.wait_forever() is idle

[p.colbert]

This is the central question:

@p.colbert

I’ve seen, from a Raspberry Pi example, how new threads can be created after anvil.server.wait_forever() has been called, from within a anvil.server.wait_forever()-spawned thread. A second @anvil.server.callable function was defined just to spawn this thread.

But does it have to be that way? Could the Uplink program usefully spawn its own threads before calling anvil.server.wait_forever()?

The SimpleQueue management is just an example of why an Uplink program might want to have its own thread created in advance of calling anvil.server.wait_forever().

I haven’t found an example of creating such a thread in advance. That might be because

1. I haven’t looked hard enough, or
2. there’s a really good reason not to do it, or
3. it’s too trivially good/bad an idea to even discuss.

But given my complete lack of experience with threads, particularly in Anvil, I really don’t know which, at this point.

My “pre-created thread” idea is still at the design stage. It’ll progress to a test-bed if it looks promising.