Some initial thoughts:
- There should be a central name registry, to avoid clashing on namespace/database names, package names etc between different package providers.
- Consider assigning a top-level reserved package name (also prefix for globals and routines), and a namespace/database prefix, to avoid clashes with names that end-users of the tools might pick.
- What's the upper limit on namespaces? Databases? Any relevant constraints for Community Edition of IRIS?
- Adding a namespace for each tool package will lengthen namespace lists in Studio, Portal etc. Maybe tools don't always need a namespace in front of their database. Ones that present a web app / REST interface probably do (at the moment) because of how the app config has to point to a namespace.
- Tools should be able to register stuff that needs to be run during environment startup and shutdown. The current need to create/edit %ZSTART / %ZSTOP routines is clunky.
- Log in to post comments