using the pubsub capability of redis to be updated with config changes

[osher]

Hi

Before creating our own implementation, I was researching the scene for a Redis based configuration solution with in-memory fallback, and got here - which is awsome! (My last visit to nconf was years ago, back then we chose another solution)

Now, assume that we use redis as the central configuration server, and would like to keep all clients in sync for config changes pushed to the sever - the natural choice would be to use the pubsub capabilities of redis, to keep all subscribed clients in sync with changes - thus, allowing the end users to use synchronous API - just like with memory storage.

I'm very hoping I'm not the first one to think about it...

Thoughts? References? Advices?

If it means submitting a new nconf-storage - it's considerable too, if I get some guidance to be sure I'm coding in accord to your paradigm. I've used rediss pubsub channels with node for a chat, and it works like a charm. Sure a configuration center will be easier than that...

Thanks Osher

[fruch]

Why do you synchronized calls ? For it to work faster ?

[amazing-gao]

I have the some idea.It will be very convenient.

[fruch]

I've found node-config-live which does exactly this, it works wit node-config-live, I guess it could work with nconf easily