Hi Shaun, Let me see if I understand the use case. Does each user specify in the Oxygen Preferences->"Global" page a custom "Frameworks Directory" which is in fact mapped on a network share? We advocate this use case when you do not want users to have individual copies of the modified frameworks. This is also nice because you make a modification in one place and have it reflected automatically in all user local installations. One other way to do this would be to have users use a collaboration tool like Subversion (SVN) in which they all check out and commit to a central repository. Then have the frameworks committed to the repository and each user work with a local copy of the frameworks which they update periodically. An Oxygen framework usually contains all additional resources needed to work with an XML: file templates, CSS files for rendering in the Author, associated DTDs or schemas. The CSS files are usually read once when an XML file is opened in the Author page. The DTDs are usually read more frequently, once on open and then each time modifications occur in the document and the editor rechecks the XML document (automatic validation, enabled by default). Regards, Radu Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 12/22/2010 10:25 PM, McDonald, Shaun wrote:

Hi,

Are there any performance costs to networking a single framework for multiple users? Say, 10-20 users might simultaneously open disparate files that invoke the same DTA rule.

This would be networked via Active Directory to Windows machines.

Thanks,

Shaun

_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user