esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darren Hague <>
Subject Re: ...about requirements collection for David work packages
Date Thu, 01 Jan 2009 12:55:30 GMT
I commented on Daniel's initial thoughts at and on of the things that 
came up was the need to work on an ESME Kernel API for plugins to use.

I thought that a Wiki would be the best place to collaborate on this - 
does anyone know if there is an appropriate Wiki space at Apache that we 
can use for this kind of collaboration (a Confluence instance, 
perhaps)?  The Incubator wiki seems to be dominated by Proposals & 
Reports, so is probably not appropriate for this sort of thing.


Daniel Koller wrote:
> 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..."
> , 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

View raw message