define request resources as a subresource

[khardaw]

I'd to be able to define a request resource like request-resource Audience::DeleteRows

Currently I am instead doing

async action Audience::DeleteRows

My understanding is that for long running processes it's best to use the request-resource model and not the action model. The reasoning being that long running processes should be accessible as permanent resources and not ephemeral actions. I definitely could be mistaken and can continue to use actions if this is not the case.

[liveandrew]

request resources are there for heavy weight long running actions, which require metadata and status. i'll phase these out probably & bring them back in if we ever standardize on heavyweight requests - use async stuff as a preference. i'll remove from the docs, or at least put in an appendix