Start collecting the requirements and just send them to the esme-dev mailing list and we'll collect them as we work on the esme roadmap. You could also add them to the esme JIRA. D.
________________________________ From: Daniel Koller [mailto:[email protected]] Sent: Sun 12/21/2008 14:41 To: [email protected] Subject: ...about requirements collection for David work packages Hi all, as a part to start on the listed work packages I would like to put down some requirements regarding the topic "...Internal APIs and plugin mechanism. ESME needs a way for external code to be plugged into it beyond what's available via REST. This might include mechanisms for authentication/authorization, hooks into message routing and access control, etc. I expect that the internal API/plugin mechanism will lead to commercial ESME plugins that will allow a commercial ecosystem toevolve around ESME..." ,...as there already some requirements going around in my head. Some questions: - Is it ok to start collecting requirements now, (or anything planned before that), and - Are there any standards to be kept in mind? (e.g. one set of requirements for all work packages?) Kind regards, Daniel -- --- Daniel Koller Jahnstrasse 20 80469 München * [email protected]
