Update patch set 2

Patch Set 2:

(1 comment)

Patch-set: 2

587b36b7c7f3423e98fcb95eb32b8f71b36fe066

@@ -309,6 +309,24 @@
       "message": "Something that comes to mind - and I suspect it is a non-issue are python applications that use non-native libraries (e.g. mysql, etc) and would they be impacted in anyway. Does the scheme at any point combine any form of process contexts for those third party libs where they might be multiple apps sharing memory, locks or other resources where they previously didn\u0027t. I can\u0027t see how honestly because IIUC, the various services are still running as separate containers but I thought I\u0027d bring it up in case I\u0027m mistaken.",
       "revId": "587b36b7c7f3423e98fcb95eb32b8f71b36fe066",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "9d446c52_73a5dd12",
+        "filename": "specs/yoga/compact-wsgi-footprint.rst",
+        "patchSetId": 2
+      },
+      "lineNbr": 116,
+      "author": {
+        "id": 6926
+      },
+      "writtenOn": "2021-11-22T13:32:08Z",
+      "side": 1,
+      "message": "We do not expect to make it all thread safe, no. For example, Nova has global state like db object that should not be shared across threads. Multiple process / singe thread MPM config should be always used I\u0027d say. But even then there might be dragons: like can\u0027t safely reload  nova-api (and placement?) into the same python interpreter. That\u0027s because of the module level globals use to connect to DB and MQ that might have re-initialization problems.",
+      "parentUuid": "b7f2779d_efa2b36d",
+      "revId": "587b36b7c7f3423e98fcb95eb32b8f71b36fe066",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
     }
   ]
 }