It's always nice to see how new technologies can be leveraged to acheive
something, and this looks like a good example of how to use DXL to alter parts
of a DB's design.
Now for the 'why?'. I've always implemented image resources as a seperate DB,
as the image resources design option was introduce in r5 (or was it 4.6) and
I've been doing this longer than that. Resources as a DB have always seemed
better as you have full control through the ACL and roles to define how and who
manipulates the resources. Also, the resources can be plain text or binary
depending on your need.
Anyone know if there are performance implications to this approach versus image
resources? If you set the view to only recalculate periodically, I'm not sure
there is one.