What to use instead of HttpContext when using OWIN without System.Web

Question

We currently have a NancyFx project that we have wired up using OWIN. We are not using System.Web and we need some place to put our context that lives for the life of a request other than HttpContext. We have started implementing the context on a thread static variable so we can access the context anywhere in the application but we are worried that using Async calls will lose this thread static context.

What do you use as a static accessor in lue of HttpContext when you divorce yourself from System.Web?

score 2 · Answer 1 · answered May 22 '14 at 18:59

2

You can use the NancyContext instead. The Items dictionary on the NancyContext is for storing per-request objects. The NancyContext is available most anywhere in a Nancy application.

answered May 22 '14 at 18:59

Christian Horsdal

4,914
23
24

Can you statically access the NancyContext? We don't want to pass around the context to every single method we need it in. – Braden May 22 '14 at 19:24
No, but it is available as a property on NancyModule, and as a parameter to Before, After, OnError hooks. Where do you need it from? – Christian Horsdal May 22 '14 at 20:20
Currently we stuff things in the HttpContext about the state of the request and pull from that context anywhere in the application. We store non-business level objects in the HttpContext so we do not have to pass them around through every method we call. IIS manages the HttpContext per request so we always have a static accessor to our context from anywhere in the application. – Braden May 22 '14 at 20:44
1

I guess you could get away with just passing the NancyContext around. – Christian Horsdal May 22 '14 at 20:58
Making HttpContext.Current static was the worst thing MS ever did, so many poorly designed applications as a result... – Phill May 23 '14 at 14:36
I haven't tested this out completely, but I'm trying to use Thread.SetData() and Thread.GetData() in order to store per requests objects. From what I understand .net spins up a new thread per request. Again, haven't tested this out fully, but hoping it will help. – The Pax Bisonica Oct 02 '14 at 20:16
@the pax bisonica: That depends on the host, and only works as long as your code doesn't switch thread e.g. by async/await. – Christian Horsdal Oct 05 '14 at 12:25

score 1 · Answer 2 · answered May 13 '15 at 10:39

This thread might answer your question : https://groups.google.com/forum/#!topic/nancy-web-framework/yILM4ZMrsSQ

public class Bootstrapper : DefaultNancyBootstrapper
{
    protected override void ConfigureRequestContainer(
        TinyIoCContainer container, NancyContext context)
    {
        base.ConfigureRequestContainer(container, context);
        container.Register<ICurrentRequest>(
          (c, o) => new CurrentRequest(context));
    }

    private class CurrentRequest : ICurrentRequest
    {
        public CurrentRequest(NancyContext context)
        {
            this.Context = context;
        }

        public NancyContext Context { get; private set; }
    }
}

What to use instead of HttpContext when using OWIN without System.Web

2 Answers2

Linked