I wonder if we could make a factory for GreenAsyncPile's on a base wsgi application class such that when you get a pile it has the property of always passing in it's app's logger's thread locals into a wapped version of your spawned callable that fixes the locals inside of the spawn before calling your function...
Or maybe a TransactionIDPreservingGreenAsyncPile class that takes a logger... that's probably simpler - we might even be able to audit for usage of GreenAsyncPile...
I wonder if we could make a factory for GreenAsyncPile's on a base wsgi application class such that when you get a pile it has the property of always passing in it's app's logger's thread locals into a wapped version of your spawned callable that fixes the locals inside of the spawn before calling your function...
Or maybe a TransactionIDPr eservingGreenAs yncPile class that takes a logger... that's probably simpler - we might even be able to audit for usage of GreenAsyncPile...