Perforce is mainly build around a client-server architecture
Perforce Proxy is mainly used to handle a big network community. This is mainly build around a client-server architecture. A central repository stores the files and metadata for source code,graphics,documentation etc.Users modify and add files on their local machines and use a range of Perforce client interfaces and integration to access the Perforce Server and obtain updated versions for the file. Please let me know if you have further queries.
We have a development center in India from where Developers work on perforce via a VPN connection. Working on a remote Perforce Server via VPN is very time consuming and slow so we are looking for alternate solutions.
The solution we are trying out currently is Perforce Proxy. We currently have a Proxy installed in India. The files are checked out in the Proxy and worked on a local machine in India. However, the changes we made cannot be tested since the Perforce Proxy in India cannot connect to the DB Servers in the US.
1.Is there a way to sync files from Perforce Proxy in India to Development Server in the US either periodically or manually
2.Is Perforce Replication some other technology other than Proxy? Will that be a feasible solution for our architecture?