[sr-dev] [SR-Users] Update existing module or create new?

[Henning Westerholt]

Am Dienstag, 5. Februar 2013, 12:52:19 schrieb Charles Chance:
> We are working on a memcached module which uses the libmemcached library, as
> opposed to the (no longer under active development) libmemcache that the
> existing module depends on.
> 
> Am I correct in thinking that in this instance, it would be better to create
> a brand new module (with a different name) rather than modify the existing
> one? In addition to changing the dependency, we will also be exporting new
> commands and potentially changing the format of the exported PVs.

Hello Charles,

as the original author of the module I'd think that changing or replacing the 
existing module would be the way to go. So far I'd not recieved that much of 
bug reports against the existing module. And as Alex Balashov also mentioned 
recently, there are some other issues with the current library.

If existing users need to stay with the old module, its available in the git 
and the existing releases, for the new release we should go with a module 
which supports the newer library.

It would be nice if you could stay with the existing PV API, which I modelled 
somehow after the htable module. If you need to change something, just 
announce it on the devel list and ask for feedback.

Thanks and regards,

Henning Westerholt