Blueprint.Core and Blueprint.Api should no nothing about HTTP semantics to allow it to more easily adapt to CLI and Background tasks.
[ ] Remove HttpContext and related from ApiOperationContext
[ ] Enable augmentation of ApiOperationDescriptor with additional properties and scanning conventions, removing HTTP-specific items such as Url (unless we decide that would still be beneficial as an identifier?
[ ] Make OperationResult less HTTP-specific. Split out handlers so that different hosts can register different handlers (i.e. CLI may just rethrow UnexpectedExceptionResult whereas HTTP turns it in to a JSON (or similar) result
Blueprint.CoreandBlueprint.Apishould no nothing about HTTP semantics to allow it to more easily adapt to CLI and Background tasks.ApiOperationContextApiOperationDescriptorwith additional properties and scanning conventions, removing HTTP-specific items such as Url (unless we decide that would still be beneficial as an identifier?OperationResultless HTTP-specific. Split out handlers so that different hosts can register different handlers (i.e. CLI may just rethrow UnexpectedExceptionResult whereas HTTP turns it in to a JSON (or similar) result