Authcache Boost was introduced in a proof-of-concept state. I hoped that it will help advancing the Boost project in a way such that Authcache can better make use of it. Regrettably this did not happen and as a result the Authcache Boost integration still requires users to apply patches. Also the Authcache Boost still needs to modify the way Boost works in a rather invasive way.

This is not something which I would want to support in the long run. Therefore I think it is best to split out the Authcache Boost module into its own project on drupal.org. This makes it also possible to be honest about its state .I.e. it is not alpha or beta, and it will never make it to a stable release unless the Boost project incorporates some of the patches.

I'm sorry that this happens but I think it is inevitable for a 7.x-2.0 release of Authcache.

Comments

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

What issues in boost need to be committed?

znerol’s picture

znerol CreditAttribution: znerol commented

Oh, thanks for commenting here @mikeytown2:

The PoC issue was: #1932444: Boost as Authcache Backend. Linked from there is #1942848: Introduce optional Vary Cookie header in generated .htaccess files in cache directory. Both of them are not really relevant (the latter as long as the browser gets a Cache-Control: no-cache.

The main thing is that there is no proper API in boost to support cache variations: #1949504: Support multiple cache directories

Also I had reports that cache-exclusion rules from boost interfered with those from authcache. In an ideal world boost would export a function usable by authcache which just writes the cache to the disk - no question asked...

  • znerol committed ca52c8f on 7.x-2.x 
    Issue #2349495: Move Authcache Boost to its own project
znerol’s picture

znerol CreditAttribution: znerol commented
Status: Active » Fixed

Moved to a separate project.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.