Can the Perforce Proxy Function as a Remote Depot?

Info & Tags

Article #:
640
Created:
02/19/07
Modified:
06/03/08
Tags:
p4p, proxy, remote depot

Related Articles

  1. Determining If A File Is Sent From The Proxy Or The Server
  2. Perforce Proxy (P4P)
  3. The Perforce Proxy (P4P)
  4. Installing P4WSAD Using an HTTP Proxy

SUMMARY

The Perforce Proxy cannot function as a remote depot, or be used to speed up the link between one Perforce Server and another by proxying files a from a remote depot.

DETAILS

The remote depot protocol is different from the normal Perforce client/server protocol. The Perforce Proxy uses the same protocol as the Perforce Server. Since the proxy protocol is incompatible with the remote depot protocol, it cannot be inserted in the network link between a local and remote depot. The Perforce Proxy can be used to connect to a Perforce Server that contains remote depots, but again, the proxy cannot connect directly to a remote depot, or be configured to serve as a remote depot.

Prior to the 2006.2 Perforce Server release, attempting to connect to a remote depot using a proxy will result in the proxy logging an error about this configuration ("can not proxy for remote depots") and an error at the Perforce Server about being unable to access the remote depot and an error at the Perforce client, as well. Beginning with the 2006.2 Perforce Server release, no server or client error is issued for this configuration. In any case, a proxy configured as a remote depot will not cache files and this configuration is not supported.

Please consult the Perforce Proxy release notes for the latest details on proxy functionality.