Redis::Objects methods need better name-spacing

[UniIsland]

The instance method names Redis::Objects currently takes (value,list,lock,set,etc) are too common, and can easily conflict with existing methods or method from 3rd party plugins.

Should we add a redis_ prefix, for instance, to the methods names?

I'd love to help out write the patch when the discussion gets a result.

[SFEley]

I think prefixing all the methods would be far too ugly for typical use. A single class bringing in so many dependencies that the developer can't keep track of where its methods are coming from probably has opportunities to be broken up or simplified. (Yes, I know, ActiveRecord. That's part of why I don't like to use it.)

I think a better answer would be an optional module that brought in Redis::Objects, but used alias_method and remove_method to rename all of its methods with the redis_ prefix. You could call it Redis::Objects::Aliased for clarity, and you could even automate the renaming with the appropriate hook methods.

[nateware]

Have you hit this in real world usage, or is this theoretical?

[UniIsland]

Added a real world usage in #196 ;)

[ShiningRay]

At least we should output a "Warning: overwrite method" to developers.

[nateware]

Closing as changing the namespace this late into the library's lifetime would be very disruptive.