Why is iungo distributed as .zexp-File and not as a file-system-based product?
iungo connects already existing and well tested frameworks with just a few lines of code. This code can easily be maintained “through the web”. iungo also tries to overcome a builtin zope-limitation: A single Zope-Instance can only keep with one version of a product. If you need different versions, you’ll need to setup different Zopes. This is a maintainance-nightmare, so iungo provides the possibility to be used in different versions within one Zope-Instance. iungo is therefore very ISP-friendly…
Related Questions
- Do I have to pay royalties to the creator of purchased products every time my final product, which includes the creators product, is distributed?
- If I identify something as Product Identity that was previously distributed as Open Game Content, does the material become Product Identity?
- Why is iungo distributed as .zexp-File and not as a file-system-based product?
