On 06/27/2013 06:46 AM, Andrew Stitcher wrote:
I think that we should minimise our use of modules and try to remove
those we already have - either stop building them as plugins or
remove them altogether.
Thoughts?
Personally I'm not overly concerned whether a module is compiled in to
qpidd itself or compiled as a separately loaded library.
What _is_ important is having optional functionality - optional both at
build time and at runtime.
It's also important to keep improving the modularity of the code,
regardless of how things are compiled. The use of plugins is certainly
not a panacea in that regard, but it has forced some extra work to keep
things decoupled which has been valuable.
Specifically regarding the xml exchange, I think keeping that as a
module makes sense as you say. I certainly wouldn't want to remove it
without a more compelling reason to do so. The code does get tested, it
has been used (though much less commonly than any of the standard
exchanges) and it doesn't pose much of a maintenance burden.
(You also missed the ha module from your list).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
