Tables vs. Resources on DSLite

I was playing with DSLite today when I noticed that the newDSLiteServer can take both tables and resources.


A named list of data.frames representing the harmonized tables.


A named list of resourcer::Resource objects representing accessible data or computation resources.

Until now I had ignored resources completely. If I understand correctly, a resource can be resolved dynamically (at runtime) unlike tables which remain static. Is that correct?