apache
In srm pull mode, the site receiving the file is contacted by the srmcp client and determines whether it is COPY or not.
In srm push mode, the site delivering the file is contacted.

For 3rd party transfers, the site contacted by srmcp then becomes a client to the other site.
On the other site the transfer is a either a GET or a PUT depending on what that client is doing.

Transfers to FNAL:
                   Pull - FNAL site: COPY, client site: GET
                   Push - FNAL site: PUT,  client site: COPY

Transfers from FNAL:
                    Pull - FNAL site: GET,  client site: COPY
                    Push - FNAL site: COPY, client site: PUT

Pull mode is efficient on both ends and push mode is efficient only on the delivering end.
From a FNAL perspective, the only mode that is bad for us is "To FNAL, Push mode".

                                 SUMMARY
SRM COPY Request Counts
psql: could not connect to server: Connection refused
	Is the server running on host "cmsdca2" and accepting
	TCP/IP connections on port 5432?
SRM GET Request Counts
psql: could not connect to server: Connection refused
	Is the server running on host "cmsdca2" and accepting
	TCP/IP connections on port 5432?
SRM PUT Request Counts
psql: could not connect to server: Connection refused
	Is the server running on host "cmsdca2" and accepting
	TCP/IP connections on port 5432?

SRM COPY
psql: could not connect to server: Connection refused
	Is the server running on host "cmsdca2" and accepting
	TCP/IP connections on port 5432?

SRM PUT -These are not efficient since they use the adapter at FNAL
psql: could not connect to server: Connection refused
	Is the server running on host "cmsdca2" and accepting
	TCP/IP connections on port 5432?

SRM GET
psql: could not connect to server: Connection refused
	Is the server running on host "cmsdca2" and accepting
	TCP/IP connections on port 5432?