On 29 Apr 2013, at 13:35, Aaron Hurt <ahurt@ena.com> wrote:
I am currently developing a module to store accounting data directly into Couchbase as JSON documents and noticed a fairly large difference between the release_3_0_0_beta0 tag and latest master. That being said I understand the beta tag is over 8 months old at this point and there is a milestone in approximately 20 days for 3.0.0 release. Would it be safe to assume that the module API structure currently in master is fairly fixed for the 3.0.0 release at this point?
If you stick to the API and don't modify the attribute lists directly then you should be ok. We may cleanup the names of API functions to make it more consistent before 3.0, but these would be simple fixes on your side. If you are considering contributing the module back, please use the connections API to manage the connection pool to Couchbase, we will not accept modules that manage their own connection pools. If it can be developed as a driver for rlm_sql (despite the name there's not too much sql specific stuff in there), then that would be ideal. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team