[ Jim Abramson ]: ------------------ | > My situation | > involves, on the one hand, a sizeable 'instance space' application, and | > on the other, some python modules/packages that I need to teach the | > instance-space stuff to use. The instance app is too vast to | > realistically rewrite as a zope Product all in one shot - therefore I'm | > looking for a sane way to gradually add external functionality (and | > later, offload existing functionality from instance -> external). What | > I'm most interested in is a discussion of External Methods vs. Products | > as a means for doing this, memory and performance considerations, etc. [ Tres Seaver ]: ------------------ | Write a simple Zope product which provides a "façade" object for your | package; then add an instance of that object to your Zope, and have | your templates / scripts use the external library through it. In a CMF | / Plone application, such an object would be a "tool". [ Jim Abramson ]: ------------------ | > The external code should know nothing about Zope, ZODB etc - so I What about making the 'external code' into a Zeo client app sharing the same Zeo server with your Zope app ? Tres suggestion is probably cleaner though. best regards, Senra