I am using WCF for data services only (ie internal to the application and very lean with no session state etc) to keep our web application scalable. We need to provide some common properties for every service call that we are currently passing in all the time. Having single request objects for every call is not ideal as beyond these common properties, the rest are very varied and change quite frequently during development.At the moment I'm considering using custom headers and the clientmessageinspector to do to set the values. Is this the simplest recommended approach for this scenario or is there a better approach?NOTE: Please remember this is for within an n-tier environment with a lightweight and common rollout cycle so we are not concerned about versioning or backwards compatibility - only speed. We are also adamant about not turning ASP.NET compatibility mode and the unnecessary performance hit that comes with it for internal data services.