C#: Anything wrong with setting HttpContext.Current in a parallel thread?

I’m using a library that relies on HttpContext.Current. The library is Facebook C# SDK, but my question should apply in other scenarios as well. I’d like to use this library from inside of a parallel thread. However, HttpContext.Current is not available in the parallel thread, so I’m thinking about caching it to a local variable and then setting it in the parallel thread like this:

Login using Facebook Problem after logging out

I am using facebook sdk and facebook connect for integrating fb into my site using asp.net and c#. The user can login using the code successfully. The problem that I face is that whenever a user is logged in thru fb; if the user logs out from the facebook’s site and then tries to login through my site using fb connect, it gives error: The session is invalid because the user logged out.