Hi Christian,
thanks for moving the discussion here!
Just to get everyone on track: A Flow Resource currently represents a pointer to a persisted binary blob aka file.
It is an entity, thus a representation will live in the database even if the actual file contents are somewhere in the cloud.
Resource was fitting name obviously, but it didn’t explicitly imply the persisted nature.
Even less specific is anything that ends in *Object because every class represents an object.
I like File because it we already use that term for exactly what a resource is (even though a file can also mean a lot more as does “resource” and especially “object”).
Follow-up question: What about related classes like ResourceManager?
Did we write down that policy somewhere?