Common use of Server Side Implementations Clause in Contracts

Server Side Implementations. For server side implementations (e.g., XML implementations), each AFC Request (a) must be from a list of Valid IP Addresses approved by Google for the AFC Service; (b) must contain a Client ID approved by Google for the AFC Service; and (c) must include Subscriber IP address and user agent information. Upon Google’s receipt of an AFC Request as described above, Google shall transmit AFC Results Set, to the extent available, via Google’s network interface in accordance with the AFC Protocol. Customer shall then display, in each instance, the entire AFC Results Set that corresponds to such AFC Request on the applicable AFC Site in the manner contemplated by this Agreement, without editing, filtering, reordering, truncating, adding content to or otherwise modifying such AFC Results Set. Customer shall not send more than one (1) AFC Request per pageview unless otherwise authorized by Google.

Server Side Implementations. For server side implementations (e.g., XML implementations), each AFC Request (a) must be from a list of Valid IP Addresses approved by Google for the AFC Service; (b) must contain a Client ID approved by Google for the AFC Service; and (c) must include Subscriber End User IP address and user agent information. Upon Google’s receipt of an AFC Request as described above, . Google shall will transmit AFC Results Set, to the extent available, via Google’s network interface in accordance with the AFC Protocol. , Customer shall then display, in each instance, the entire AFC Results Set that corresponds to such AFC Request on the applicable AFC Site in the manner contemplated by this Agreement, without editing, filtering, reordering, truncating, adding content to or otherwise modifying such AFC Results Set. Customer shall will not send more than one (1) AFC Request per pageview unless otherwise authorized by Google.