Multiple resource parts for the same resource

[dkrasner]

Main issues

Creating multiple resource parts (&views) on the same resource can create all sorts of clash issues. For example, if the resource assume last call results to be stored somewhere and multiple parts are invoking these calls there is no good way to keep things in check.

Perhaps resources should be classes and resource parts create instances of those classes, or something JS similar.