Hello, Bob. I also first suggested something like that, as common folders, common "public" databases. However Aaron explained that such tool as workers enables separate Gears applications cross-talk. To make your site's Gears stuff be available from other sites you just should provide a script that has a worker inside, providing functional interface to other origins. However you cannot make something that surpasses the general Gears abilities. As access to local file system etc. I guess that it is possible to make Gears sites into cross-talking peer-to-peer network For example, if you make a Gears extension (that is, a site with Gears lib, and with a "public interface" worker-script(s)) for reading some RSS, and I make an on/offline Chinese-English dictionary database, then third-party sites may access your reader and my dictionary. So, in a way, our Gears systems are "extensions".
Gears is restricted by safety constraints. If your scripts and my database are in public folder, and/or everybody may access local files, then it is easy to drop my table and delete your script files, as well as examine the content of /My Documents/ folder...
