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
/home/enstore/dcache-deploy/dcache-fermi-config/active.srm.transfers: line 59: /usr/local/pgsql/bin/psql: No such file or directory
SRM GET Request Counts
/home/enstore/dcache-deploy/dcache-fermi-config/active.srm.transfers: line 62: /usr/local/pgsql/bin/psql: No such file or directory
SRM PUT Request Counts
/home/enstore/dcache-deploy/dcache-fermi-config/active.srm.transfers: line 67: /usr/local/pgsql/bin/psql: No such file or directory

SRM COPY
/home/enstore/dcache-deploy/dcache-fermi-config/active.srm.transfers: line 73: /usr/local/pgsql/bin/psql: No such file or directory

SRM PUT -These are not efficient since they use the adapter at FNAL
/home/enstore/dcache-deploy/dcache-fermi-config/active.srm.transfers: line 87: /usr/local/pgsql/bin/psql: No such file or directory

SRM GET
/home/enstore/dcache-deploy/dcache-fermi-config/active.srm.transfers: line 98: /usr/local/pgsql/bin/psql: No such file or directory