Skip to main content

A DD4T.net Implementation - Navigation (part 2)

In previous post, Navigation, I presented the foundation for deserializing the navigation XML into an object model. In this post, I'll continue presenting the NavigationFactory class and the integration with caching.

The NavigationFactory class is a singleton wired through dependency injection (such as Ninject) that uses caching to serve navigation object model for a given Publication.

[Inject]
public virtual ICacheWrapper CacheWrapper { get; set; }

public Navigation GetNavigation()
{
    string publicationUrl = UriHelper.GetPublicationUrl(HttpContext.Current);
    string key = GetKey(publicationUrl);

    Navigation navigation;
    object cacheElement;
    if (!CacheWrapper.TryGet(key, out cacheElement))
    {
        string virtualPath = publicationUrl + "system/navigation.xml";
        string filePath = HttpContext.Current.Request.MapPath(virtualPath);
        navigation = ParseXml<Navigation>(filePath);
        SetParent(navigation);

        if (navigation == null)
        {
            CacheWrapper.Insert(key, false, 1);
        }
        else
        {
            CacheWrapper.Insert(key, navigation, 60);
        }
    }
    else
    {
        navigation = cacheElement as Navigation;
    }

    return navigation;
}

Notice the following:
  • The returned navigation object model depends on the Publication identified for the current request. They method GetPublicationUrl from class UriHelper returns the first level folder of the URL path, which helps us identify the Publication;
  • Method ParseXml was presented in my previous post, mentioned above, and is in charge with deserializing the XML into an object model;
  • A null Navigation object is cached for one minute, just to make performance better, in case the navigation XML is somehow missing or not deserializeable; otherwise, the navigation object is cached for one hour;
  • For simplicity sake of this example, the code uses hard-coded values for cache times and the XML navigation path is "/system/navigation.xml" under the PublicationUrl;
  • Method SetParent is used to create the reference from child navigation item to its parent. Initially, the navigation XML contains only information about parent navigation item to its children, but in practice we also need the capability to traverse the navigation model upward;

private void SetParent(Navigation navigation)
{
    if (navigation == null)
    {
        return;
    }

    foreach (NavigationItem item in navigation.Items)
    {
        SetParent(item);
    }
}

private void SetParent(NavigationItem item)
{
    if (item == null || item.ChildItems == null)
    {
        return;
    }

    foreach (NavigationItem child in item.ChildItems)
    {
        child.ParentItem = item;
        SetParent(child);
    }
}

A useful method is GetNavigation(Navigation object) which gives us an array of NavigationItem objects situated under the 'root' Structure Group in the navigation model.

public NavigationItem[] GetNavigation(Navigation navigation)
{
    if (navigation == null || navigation.Items.IsNullOrEmpty())
    {
        return new NavigationItem[0];
    }

    NavigationItem[] childItems = navigation.Items[0].ChildItems;

    return childItems == null ? new NavigationItem[0] : childItems;
}

The code above is wired in Ninject using the following construct:

Bind<INavigationFactory>().To<NavigationFactory>().InSingletonScope();

Also, client code make use of the navigation using the following constructs:

INavigationFactory factory = DependencyResolver.Current.GetService<INavigationFactory>();
Navigation navigation = factory.GetNavigation();
NavigationItem[] items = factory.GetNavigation(navigation);


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

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

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