Cross-process postMessage

chrome/common/chrome_content_client.cc

Index: chrome/common/chrome_content_client.cc
diff --git a/chrome/common/chrome_content_client.cc b/chrome/common/chrome_content_client.cc
index da07553e0035a9963a9ae744510393aca1742108..4edb066031d82fb275734f8456edaf6f1977ba9e 100644
--- a/chrome/common/chrome_content_client.cc
+++ b/chrome/common/chrome_content_client.cc
@@ -299,24 +299,12 @@ void ChromeContentClient::AddNPAPIPlugins(
 #endif
 }
 
-bool ChromeContentClient::CanSendWhileSwappedOut(const IPC::Message* msg) {
-  // Any Chrome-specific messages that must be allowed to be sent from swapped
-  // out renderers.
-  switch (msg->type()) {
-    case ChromeViewHostMsg_DomOperationResponse::ID:
-      return true;
-    default:
-      break;
-  }
-  return false;
-}
-
 bool ChromeContentClient::CanHandleWhileSwappedOut(
     const IPC::Message& msg) {
-  // Any Chrome-specific messages (apart from those listed in
-  // CanSendWhileSwappedOut) that must be handled by the browser when sent from
-  // swapped out renderers.
+  // Any Chrome-specific messages that must be handled by the browser when sent
+  // from swapped out renderers.
   switch (msg.type()) {
+    case ChromeViewHostMsg_DomOperationResponse::ID:

[Charlie Reis, 2011/12/01 23:13:02]

Is this a worthwhile change independent of the rest of the code, or is it only
needed when we change about:swappedout?  Just wondering if we should land it in
its own CL.

[supersat, 2011/12/09 23:08:20]

It's only needed if we change about:swappedout.

[Charlie Reis, 2011/12/12 22:20:36]

Ok.  It's still there in patch set 2, so you should probably remove it.

[supersat, 2011/12/15 19:30:49]

Done. Not sure why it wasn't in patch set 2.

     case ChromeViewHostMsg_Snapshot::ID:
       return true;
     default: