Object based caching

[konstin]

liboparl should use object based caching as opposed to request based caching so that objects that have already been retrieved through a list do not need to be loaded again when requested individually.

(I'm aware that a user could already implement that in the resolve function. But they'd need to parse the object themselves which would self-defeating for a liboparl user)

[eFrane]

I'd rather vote for it should offer both object-based and request-based caching. My reasoning is that for some applications it might be very much okay to just keep raw request data around (mirrors for instance) as they don't actually care much about the contents whereas other applications that work with the object contents might not want to keep the request data around but do have the objects.

[konstin]

For simple mirroring you don't need liboparl, so the main mode for liboparl users will be object base caching. Object based caching can also improve performance significantly.