Until now we have only considered the storage of data in the ZODB, the native database of Zope and hence of Plone. As we stated earlier, the ZODB is not optimized for binary data. A big ZODB with a lot of BLOBs inside will become slow and hard to manage (pack, back up, and so on). There is a very simple solution for working around this downside. The answer is "links". Linking content is the vitality motor of the Web, as we know it. Although linking people seems to get more important in Web 2.0, linking content is classic.
We can do linking content with Plone. In the chapters for audio and video, we saw the collective.flowplayer
product. This product allows us to integrate external multimedia content as link objects. Plone does neither the storage nor the publishing of this data. Everything is handled by an external web server. Something similar can be done with the collective.plonetruegallery
gallery product with images. It is possible to include images from...