Move the rest of the renderer->browser messages that belong in content. Also do a bunch of cleanup:

Move the rest of the renderer->browser messages that belong in content.  Also do a bunch of cleanup:
-move safe browsing messages together
-get rid of webkit_param_traits and common_param_trait since they're no longer needed
-remove the multiple include of IPC files from places that don't need it

TBR=tsepez
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=79235

[Tom Sepez, 2011-03-24 00:51:21]

LGTM.  The compiler and linker will catch more stuff than I can manually.

http://codereview.chromium.org/6713084/diff/7091/chrome/common/automation_mes...
File chrome/common/automation_messages.cc (right):

http://codereview.chromium.org/6713084/diff/7091/chrome/common/automation_mes...
chrome/common/automation_messages.cc:680: // The traits for these are defined in
render_messages.h
Would have expected to see these in a header.

http://codereview.chromium.org/6713084/diff/7091/content/common/content_messa...
File content/common/content_message_generator.h (right):

http://codereview.chromium.org/6713084/diff/7091/content/common/content_messa...
content/common/content_message_generator.h:8: // libraries.
Nit:  maybe two #ifndef blocks to avoid saying child_process_messages twice.

[jam, 2011-03-24 01:07:56]

http://codereview.chromium.org/6713084/diff/7091/chrome/common/automation_mes...
File chrome/common/automation_messages.cc (right):

http://codereview.chromium.org/6713084/diff/7091/chrome/common/automation_mes...
chrome/common/automation_messages.cc:680: // The traits for these are defined in
render_messages.h
On 2011/03/24 00:51:21, Tom Sepez wrote:
> Would have expected to see these in a header.

yeah this is ugly, but i didn't have a clean way of dealing with it.  these
traits are generated automatically in render_messages.h, but then later I
realized they're needed here.  since i removed common_param_traits, I didn't
want to keep that just for this.  maybe we should add common_param_traits that
uses the nice macros.  wdyt?

http://codereview.chromium.org/6713084/diff/7091/content/common/content_messa...
File content/common/content_message_generator.h (right):

http://codereview.chromium.org/6713084/diff/7091/content/common/content_messa...
content/common/content_message_generator.h:8: // libraries.
On 2011/03/24 00:51:21, Tom Sepez wrote:
> Nit:  maybe two #ifndef blocks to avoid saying child_process_messages twice.

Done.

[Tom Sepez, 2011-03-24 01:12:17]

I think a common_param_traits.h that uses macros and can be multiply included is
exactly what we want here.