Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

All files from Digizuite are served using the media pipelines. From DFS 9.0.0 the media pipeline has been redesigned, however, the old is still there for compatibility reasons.

It is configurable which one is used and this is controlled by a config parameter in DFS.Settings.config:

DFS.Settings.config
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
  <sitecore>
    <settings>
		<setting name="DFS.MediaPipeline" value="dfsmedia"/>
	</settings>
  </sitecore>
</configuration>

There are two options

  • dfsmedia - the new implementation
  • media - the old implementation

The default valie is dfsmedia.

This section describes the new dfsmedia pipeline and its capabilities. For a description of the old media pipeline, see this link section 5.2.

Implementation

The new dfsmedia pipeline is implemented as a httphandler and it is accessible on the following endpoint: http(s)://<sitecore>/dfsmedia

 The code is implemented as a pipeline in Sitecore. This pipeline is located in the DFS.Services.config file:

Error rendering macro 'code': Invalid value specified for parameter 'firstline'
 <configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
  <sitecore>
	<pipelines>     
	 <DFS.Services.DFSMedia>
        <processor type="DFS.Services.Pipelines.DFSMedia.CheckSecurity, DFS.Services" />        
        <processor type="DFS.Services.Pipelines.DFSMedia.GetMediaFromCache, DFS.Services" />
        <processor type="DFS.Services.Pipelines.DFSMedia.GetMediaPrerequisites, DFS.Services" />
        <processor type="DFS.Services.Pipelines.DFSMedia.GetMediaFromDigizuite, DFS.Services" />
        <processor type="DFS.Services.Pipelines.DFSMedia.ResizeImage, DFS.Services" />
        <processor type="DFS.Services.Pipelines.DFSMedia.SaveToCache, DFS.Services" />        
     </DFS.Services.DFSMedia>
    </pipelines>
  </sitecore>
</configuration>


  • No labels