Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/sonic boom #165

Closed
wants to merge 44 commits into from
Closed

Feature/sonic boom #165

wants to merge 44 commits into from

Conversation

jaswrks
Copy link
Contributor

@jaswrks jaswrks commented Oct 21, 2015

Important files to review as a part of the work in this PR:

  • See cache.txt, which serves cache files via .htaccess and some jujumagumbo.

Noting that this is not yet MS compatible.
Noting that all of our .htaccess tweaks require Apache 2.2+

TODO

  • Update this class member so that it considers the current mode of operation.
  • Figure out how to deal with stored headers when serving cache files via .htaccess.
  • Figure out how to deal with GZIP compression coupled with the possible use of mod_asis.
  • Add a mode that will get this working on Ningx also; and perhaps resolve Cached files readable under Nginx comet-cache#435.

@@ -338,7 +348,10 @@ public function setup()
'auto_cache_delay' => '500', // In milliseconds.
'auto_cache_sitemap_url' => 'sitemap.xml', // Relative to `site_url()`.
'auto_cache_other_urls' => '', // A line-delimited list of any other URLs.
'auto_cache_user_agent' => 'WordPress',
'auto_cache_permalinks' => '1', // `0|1`; auto-cache known Post/Page permalinks?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious what these additional Auto-Cache options are for. Is there an associated GitHub issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't figured this out yet, sorry.

My thinking is that I will try pull together a list of known permalinks and archives based on what is in the DB. That way the ACE will be capable of pre-caching a site for the most part, even when it lacks an XML sitemap.

This is a part of trying to accomplish a mode whereby ZenCache options could be preconfigured in such a way to create a sonic boom with very little effort on the part of a site owner. Those two options may or may not become a part of the UI directly, but having them in there might make it possible for different modes to be preconfigured in a future release.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ha.. I am actually using the term sonic boom when I talk about ZenCache now. That's funny.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ha.. I am actually using the term sonic boom when I talk about ZenCache now.

We should totally work that into the UI somehow... "Enable (safest) | Enable (fastest) | Enable (sonic boom!)"

@jaswrks
Copy link
Contributor Author

jaswrks commented Oct 22, 2015

Adding TODO items above. Still needs research and some thought.

@raamdev
Copy link
Contributor

raamdev commented Jan 4, 2016

@jaswsinc Just a heads up: You may want to merge 000000-dev into this branch sooner rather than later. It looks like there are already some merge conflicts you'll need to resolve. :-)

@raamdev
Copy link
Contributor

raamdev commented Jan 4, 2016

Also noting that merging 000000-dev will cause the assets/ directory to now be managed under LFS.

@jaswrks
Copy link
Contributor Author

jaswrks commented Jan 6, 2016

Copy that. I'm going to leave this here for now, but I suspect I will need to start over on this effort to create a sonic boom. My feeling is that these changes for 5.4 should come first, and since that work is going to make it impossible to merge this branch in after, I'm thinking I should work on 5.4 enhancements first and come back to this later and try again.

@raamdev
Copy link
Contributor

raamdev commented Jun 3, 2016

@jaswsinc I'm wondering if you'd be able to redo this PR now that the codebase has been updated for PHP 5.4. Doing so would give me a big head-start on everything that's going to go into a new Apache Optimizations panel, including the ability to use mod_rewrite to load cached files (see wpsharks/comet-cache#783).

@raamdev
Copy link
Contributor

raamdev commented Jun 20, 2016

@jaswsinc Just noting that @renzms is currently working on several issues related to the Apache Optimizations panel (including adding the panel itself). You may want to hold off on redoing this PR until after that work:

wpsharks/comet-cache#765
wpsharks/comet-cache#764
wpsharks/comet-cache#554

@jaswrks
Copy link
Contributor Author

jaswrks commented Jun 21, 2016

Copy that. Thank you.

@jaswrks
Copy link
Contributor Author

jaswrks commented Jun 29, 2016

I'm closing this, but leaving the branch intact, for now; i.e., for future reference.

@jaswrks jaswrks closed this Jun 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants