Inconsistency with keyPrefix

[ember-cli-deploy]

Inconsistency with keyPrefix

[achambers]

Hi @pedrokost.

The functionality that you are describing is quite intentional.

It is by design that <keyPrefix>:current points to the Revision Key and not the Redis Key.

This plugin will combine the keyPrefix property and the revisionKey property to determine the Redis Key. Therefore it doesn't make sense for the revisionKey property to either accept the keyPrefix or return a value containing it. The revisionKey is supposed to be the unique value that identifies the revision.

Hope this cleared things up a bit. I'm going to close this issue as there is nothing to be changed here.

If you have any other questions or need something clarified more, by all means ask them here, or reopen this if you need to.

[pedrokost]

@achambers OK

Why wouldn't the revisionKey and the Redis Key be the same? Wouldn't this remove one possible source of confusion?

[achambers]

@pedrokost What confusion is that?

[pedrokost]

@achambers Nevermind. I only stumbled upon this because I was upgrading from ember-deploy-redis#0.0.7 to ember-cli-deploy-redis.

~~In the former prefixKey:current points to the actual HTML, but in the latter it points to a reference key. Instead the content is in prefixKey:current-content by default. ~~

I can work around this without changing the server side code by renaming activationSuffix to current-pointer and activeContentSuffix to current.

Edit: I wrote incorrectly. In ember-deploy-redis#0.0.7 prefixKey:current contained prefixKey:reference. The only way I can work around this difference seems to by changing the server code.