[doboyy]

Yeah, I think an api of that sort would quickly turn into a headache if it subtlety did code dispatch through a common interface on objects that are hardly related in reality. From a programming perspective, that kind of opaqueness is more of a mental burden than relief.

I can see a database interface being useful if you constrained the scope of what an entry is and don't allow those operations to actually modify the objects.

The extent of the scope could start at what are traditionally considered OS resources, not random blocks of texts, newsgroups, or pixels, but things that would generally be more useful to query.

Not being allowed to actually modify an entry through 'delete' presents a problem. The database and the code that is allowed to modify its state would have to be synchronized/notified on an update.

In this way, the database is a front-end to the OS.