New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curdling.web.Server
doesn't work in multi-process environment
#53
Comments
Thanks for the report! I'm about to release a new version with improvements in the overall stability of the installer and a handful of other bugs, but I feel like refactoring the indexer will be the thing for the next release. If you can think of any quicker solution for your problem, we can just take a short path for now and than iterate on the server component in the next release (after refactoring the indexer). |
@clarete I'm considering making the indexer configurable in the |
@clarete Maybe I'll also need a distributed lock to replace |
@suzaku Your idea sounds amazing to me. However, I'm still trying to kill some very basic bugs in other areas so I might take a while to be able to work on the server. The bright side is that I won't even touch that code for a while, which means that you can just go ahead and implement that if you want. I'll certainly be happy to apply the patch. I can help in one thing or another about tests, since we should definitely start adding the Thank you for your report and the valuable ideas you gave so far. |
Just a heads up, you should take a look in our Milestones. I targeted this feature to the version |
I'm trying to reuse
curdling.web.Server
to set up a curdling server in a WSGI app engine:After one of the
worker
handles anupload
, it updates itsserver.index.storage
, while theindex.storage
of the otherworkers
stay the same.The text was updated successfully, but these errors were encountered: