Edited-this is a bug or choice in lucee. See Bens’s comparison to ACF
I’m trying to implement the PUT/GET patterns for long-running processes and Futures seemed like the perfect solution. But after doing all of the refactoring to use runAsync I found that it never executes my code and I have no insight into why not. Nothing is logged in lucee and I suspect the problem is that runAsync runs in an entirely isolated space separate from the calling application. That’s not documented or hinted at anywhere, so if its true that’s a huge oversight.
Is runAsync the right solution for this pattern and I just have a too-tightly coupled application? Are coldbox’s async pipelines/futures different in this regard? Their docs say you can load the application context but that you shouldn’t, is that because the whole application loads inside the thread?
The map/reduce/each/etc functions are perfect in structure for what I’m trying to do, but they have to finish before the request completes, defeating the purpose of put/get. Any help is appreciated.
7 posts - 2 participants