DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12554>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12554 Directory System Summary: Directory System Product: Avalon Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Phoenix AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Phoenix will eventuall need a decent directory system for all of its resources. The directory service may include things like resources from jars and it may also include things like type information, profile information etc. To accomodate such a system it is first necessary to classify the possible entrys. Classifications include; * Boot-time: Is entry required during boot time or not? * Fixed vs Variable: Is the entry fixed at startup time and readonly after that or can it change after initialization. * Persistent/Non-Persistent: Will entry persist across a restart * Dynamic/Static: Is the entry dynamically created on traversal. Things like Linuxs /dev filesystem are considered dynamic as they have no physical representation but are just windows onto parts of the kernel * Scope: I entry scoped per application, per partition or per component? * Exported: Is the entry exported to some other system (ie JMX, AltRMI, CORBA etc). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
