Skip to main content

AOP using RealProxy (custom implementation) - Part I (RealProxy)

This days I read a post from MSDN Magazine about RealProxy. Using RealProxy you can control the call itself of a method, alter the result or the input. We could say that this is the door for AOP (Aspect Oriented Programming) without using a specific stack.
The most important method of RealProxy is “Invoke”. This method is called each time when a method from you specific class is called. From it you can access the method name, parameters and call your real method or a fake one.
Before saying “Wooww, it’s so cool!” you should know that this will works only when you use also the interfaces.
Reading the above article I had the idea to see if and how we can implement a duration profiling mechanism that is based on attributes. If a method from your specific implementation had the custom profiling attribute, than automatically, the system will measure how long it takes to make a specific call.
First step is to create a custom attribute, which accept a custom message that will be written when we will write the duration time to the trace.
public class DurationProfillingAttribute : Attribute
{
    public DurationProfillingAttribute(string message)
    {
        Message = message;
    }

    public DurationProfillingAttribute()
    {
        Message = string.Empty;
    }

    public string Message { get; set; }
}
Next we need is a generic class that extends RealProxy and calculate the duration of the call. In the Invoke method we will need to use a Stopwatch that will calculate how long a call takes. At this level we can check if a specific method is decorated with our attribute.
public class DurationProfilingDynamicProxy<T> : RealProxy
{
    private readonly T _decorated;

    public DurationProfilingDynamicProxy(T decorated)
        : base(typeof(T))
    {
        _decorated = decorated;
    }

    public override IMessage Invoke(IMessage msg)
    {
        IMethodCallMessage methodCall = (IMethodCallMessage)msg;
        MethodInfo methodInfo = methodCall.MethodBase as MethodInfo;
        DurationProfillingAttribute profillingAttribute = (DurationProfillingAttribute)methodInfo.GetCustomAttributes(typeof(DurationProfillingAttribute)).FirstOrDefault();

        // Method don't needs to be measured. 
        if (profillingAttribute == null)
        {
            return NormalInvoke(methodInfo, methodCall);
        }

        return ProfiledInvoke(methodInfo, methodCall, profillingAttribute.Message);
    }

    private IMessage ProfiledInvoke(MethodInfo methodInfo, IMethodCallMessage methodCall, string profiledMessage)
    {
        Stopwatch stopWatch = null;
        try
        {
            stopWatch = Stopwatch.StartNew();
            var result = InvokeMethod(methodInfo, methodCall);
            stopWatch.Stop();

            WriteMessage(profiledMessage, methodInfo.DeclaringType.FullName, methodInfo.Name, stopWatch.Elapsed);

            return new ReturnMessage(result, null, 0,
                methodCall.LogicalCallContext, methodCall);
        }
        catch (Exception e)
        {
            if (stopWatch != null
                && stopWatch.IsRunning)
            {
                stopWatch.Stop();
            }
            return new ReturnMessage(e, methodCall);
        }
    }

    private IMessage NormalInvoke(MethodInfo methodInfo, IMethodCallMessage methodCall)
    {
        try
        {
            var result = InvokeMethod(methodInfo, methodCall);

            return new ReturnMessage(result, null, 0,
                methodCall.LogicalCallContext, methodCall);
        }
        catch (Exception e)
        {
            return new ReturnMessage(e, methodCall);
        }
    }

    private object InvokeMethod(MethodInfo methodInfo, IMethodCallMessage methodCall)
    {
        object result = methodInfo.Invoke(_decorated, methodCall.InArgs);
        return result;
    }


    private void WriteMessage(string message, string className, string methodName, TimeSpan elapsedTime)
    {
        Trace.WriteLine(string.Format("Duration Profiling: '{0}' for '{1}.{2}' Duration:'{3}'", message, className,methodName, elapsedTime));
    }
We could have another approach here, calculating the duration for all the methods from the class. You can find below the classes used to test the implementation. Using "GetTransparentProxy" method we can obtain a reference to our interface.
class Program
{
    static void Main(string[] args)
    {
        DurationProfilingDynamicProxy<IFoo> fooDurationProfiling = new DurationProfilingDynamicProxy<IFoo>(new Foo());
        IFoo foo = (IFoo)fooDurationProfiling.GetTransparentProxy();

        foo.GetCurrentTime();
        foo.Concat("A", "B");
        foo.LongRunning();
        foo.NoProfiling();
    }
}

public interface IFoo
{
[DurationProfilling("Some text")]
DateTime GetCurrentTime();

[DurationProfilling]
string Concat(string a, string b);

[DurationProfilling("After 2 seconds")]
void LongRunning();

string NoProfiling();
}

public class Foo : IFoo
{
public DateTime GetCurrentTime()
{
    return DateTime.UtcNow;
}

public string Concat(string a, string b)
{
    return a + b;
}

public void LongRunning()
{
    Thread.Sleep(TimeSpan.FromSeconds(2));
}

public string NoProfiling()
{
    return "NoProfiling";
}

}
In the next post related to RealProxy we will see how we can integrate this with a IoC container to be able to control what part of the system have the duration profiling active.

Comments

  1. Interesting - isn't RealProxy a bit too tied to .Net Remoting?

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP