Remove RemoteAccessClientFirewallTraversal policy and code paths.

Remove RemoteAccessClientFirewallTraversal policy and code paths.

BUG=96318
TEST=

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

[Wez, 2011-10-13 19:53:08]

This CL removes the RemoteAccessClientFirewallTraversal policy, the associated
code to propagate policy into renderers, and the experimental Pepper API to
expose it to plugins.

ajwong: Please let me know if you think there's anything I've missed.
mnissler: Please take a look at the policies template.
ananta: Please check that this is sufficient to un-block your chrome/content
deps work.

[awong, 2011-10-13 20:00:11]

LGTM

[Mattias Nissler (ping if slow), 2011-10-13 20:55:26]

chrome/browser/policy LGTM

FYI: We're planning to add policy support for browser add-ons during Q4,
initially by laying the groundwork for policy for extensions via the extension
settings API. This may be interesting also for remoting as long as you have
extension/ppapi components in the system.

[Mattias Nissler (ping if slow), 2011-10-13 20:56:04]

chrome/browser/prefs LGTM too.

[Wez, 2011-10-13 22:18:53]

jam: FYI (and feel free to review in place of ananta@ ;)

[ananta, 2011-10-14 00:45:26]

On 2011/10/13 22:18:53, Wez wrote:
> jam: FYI (and feel free to review in place of ananta@ ;)
The changes to get rid of the IPC messages and the corresponding handlers from
content and chrome would work just fine :)

Thanks for doing this. LGTM for that part.

[jam, 2011-10-14 16:58:02]

content lgtm, thanks

[Wez, 2011-10-14 22:02:06]

dmichael: Please review ppapi/...

[Wez, 2011-10-18 22:44:05]

piman: dmichael seems busy/absent.  Would you do the honours?

[piman, 2011-10-18 22:46:01]

PPAPI LGTM