1. We don't have any in-the-box IoC solution yet for injecting dependencies into the constructor. We have an instance provider extensibility point that can be used for an IoC which we are going to explore. CommonServiceFactory on codeplex uses this for plugging
in an IoC.

2. Processors however can easily be built up by a container as you construct the processor yourself. To handle an NHib session what you would do is have a special processor that creates an NHib session (from a session factory) and then provides it as one
of it's outputs. This allows other processors to take the session as an input or the operation to access the session through one of it's parameters.

3. Processors are actually designed to be stateless with regards to the request. The same processor instance is reused across all requests. The execute method is passed all the state that the processor needs to do it's work. The processor can still have
some state, but it should not be related to the request.

I'll plan a blog post on processors to describe this in more detail. I will also work on getting our IoC prototype in place.

If supporting IoC containers is important, can you add a work item so others can vote?