Skip to main content

A DD4T.net Implementation - A Dynamic Publication Resolver

In the previous post Simple Publication Resolver, I presented a simplistic way of putting generic pages into Publication context by identifying the Publication URL by just applying a regular expression to the URL path.

In this post, I present a proper Publication Resolver algorithm, for DD4T.net, that dynamically maps Publication IDs to Publication URLs and vice versa.

The interface of a Publication Resolver defines 2 methods: GetPublicationUrl and GetPublicationId, which provide retrieval functionality for mapped Publication ID and URL.

public interface IPublicationResolver
{
    string GetPublicationUrl(int publicationId);
    int GetPublicationId(string publicationUrl);
}

The implementing class, PublicationResolver, defines an algorithm that dynamically discovers the mapped ID for a given Publication URL and the other way around. It makes use of the Tridion Content Delivery API PublicationMetaFactory to retrieve the PublicationMeta object containing information about the given Publication:

public class PublicationResolver : IPublicationResolver
{
    private readonly IDictionary<string, int> mapUrlToId =
        new Dictionary<string, int>();
    private readonly IDictionary<int, string> mapIdToUrl =
        new Dictionary<int, string>();

    public string GetPublicationUrl(int publicationId)
    {
        if (mapIdToUrl.ContainsKey(publicationId))
        {
            return mapIdToUrl[publicationId];
        }
        else
        {
            PublicationMetaFactory factory = new PublicationMetaFactory();
            PublicationMeta meta = factory.GetMeta(publicationId);
            string url = meta == null ? string.Empty : meta.PublicationUrl;

            mapIdToUrl[publicationId] = url;
            mapUrlToId[url] = publicationId;

            return url;
        }
    }

    public int GetPublicationId(string publicationUrl)
    {
        if (mapUrlToId.ContainsKey(publicationUrl))
        {
            return mapUrlToId[publicationUrl];
        }
        else
        {
            PublicationMetaFactory factory = new PublicationMetaFactory();
            PublicationMeta meta = factory.GetMetaByPublicationUrl(publicationUrl).FirstOrDefault();
            int id = meta == null ? 0 : meta.Id;

            mapIdToUrl[id] = publicationUrl;
            mapUrlToId[publicationUrl] = id;

            return id;
        }
    }
}

The interface and class above can easily be put in Ninject as singleton mapping:

Bind<IPublicationResolver>().To<PublicationResolver>().InSingletonScope();

When using the Publication Resolver, we can easily retrieve Publication ID for a given URL or the other way around. The code below defines property PublicationResolver that is injected into the current class:

[Inject]
public virtual IPublicationResolver PublicationResolver { get; set; }

...

string url = PublicationResolver.GetPublicationUrl(44);
int id = PublicationResolver.GetPublicationId("/zh/cn/");


Comments

Popular posts from this blog

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio