)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"ac2b59760ed92c7685e28f9588d0deb9b1fb7937","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6ba6e814_fe048c04","updated":"2025-07-03 16:14:10.000000000","message":"+1 just to indicate that at first glance this module should continue to works without problem if we just remove the `Server` class and not the module file.","commit_id":"5e5f4f2e3898924bef3fa7713bcbf8ef0ddde4d4"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"4d0ac659a2206f1d68e3745f70de19fe721f0588","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"95180c9a_b81a6a82","updated":"2025-07-03 16:06:41.000000000","message":"Hello Stephen,\n\nThanks for this patch.\n\nThis patch make sense and at first glance it LGTM. I just have one concern about the fact to keep the remaining classes at this level in the code tree and without binding the remaining parts of the WSGI modules to the threading backend.\n\nIndeed, the whole WSGI module was planed for removal, so the threading backend was expecting that we won\u0027t have to import it anymore. The problem, seems to be that, to continue to use the WSGI module when the threading backend is enabled, I think we have to add this module either to the binding of the threading backend or to the common modules of backend (at least the keeped classes). I\u0027m not fully sure of that.\n\nBeside this potential problem, and beside the adjustment of the deprecation warning, from a design PoV I think it would make sense to put all the remaining part into the common module as they will be shared between backends, it could be done with a follow up though if there is no problem.\n\n@dbengt@redhat.com: Please can you confirm the problem point that I expose.","commit_id":"5e5f4f2e3898924bef3fa7713bcbf8ef0ddde4d4"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"5ee00fbfd3d0e0cb074ee15e82c44c8d78cd98db","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"66b0e12e_3313f8b4","updated":"2025-07-07 08:42:43.000000000","message":"Thanks Stephen.\nLet\u0027s fix the deprecation message. Lets Daniel answer my question about the place of the WSGI module in a parallel thread, this way we won\u0027t block this patch unnecessarily.","commit_id":"5e5f4f2e3898924bef3fa7713bcbf8ef0ddde4d4"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"5870545f3676b84bf695b772dae990368dde03ae","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5d15b5a1_4523ec8b","in_reply_to":"95180c9a_b81a6a82","updated":"2025-07-03 16:09:34.000000000","message":"At first glance the wsgi backend is handled frontally and is independent from the backend logic https://github.com/search?q\u003drepo%3Aopenstack%2Foslo.service%20wsgi\u0026type\u003dcode\n\nhttps://opendev.org/openstack/oslo.service/src/branch/master/oslo_service/backend/eventlet/__init__.py\nhttps://opendev.org/openstack/oslo.service/src/branch/master/oslo_service/backend/eventlet/__init__.py","commit_id":"5e5f4f2e3898924bef3fa7713bcbf8ef0ddde4d4"}]}