I'm currently implementing sharing WebProcesses in Geary using WebKitWebView::related-view at construction time. While this seems to be successful ensuring the same WebProcess is re-used when creating multiple WebKitWebViews at the same time, if a related view is destroyed it then can't be used successfully as a related process and a new WebProcess will be launched. It is not convenient to prevent one of the old WebViews from being destroyed since they are far removed from the code that handles conversation loading, so it would be useful to have some other means of sharing WebProcesses between temporally isolated views. Bring back 1 WebContext == 1 WebProcess perhaps? It seems intuitive and would require jumping through less hoops than using webkit_web_view_new_with_related_view().