The boost module provides a very similar feature to this module.

One of the 7 principles of the Drupal project is collaboration. Would you consider merging your project into that one and collaborating with it's authors?

Otherwise, it would be great if you could document what makes this module different so that people can make a good decision about which one to use.

Comments

asak’s picture

asak commented

Yes, I agree with greggles.

This is a very intense issue, and efforts should be centralized.

Bevan’s picture

Bevan commented

#453066: How is this module different from boost? was marked duplicate

sebyoga’s picture

sebyoga commented

My module is differents for many raison :

There is an interface to manage cache at present put in cache. It is possible to forbid the stake in cache for a given page. It is possible for a given page, to put it in cache with a different expiration. There is a toolbar in front to admin cache page for current page.

The management of writing of pages is different from that of boost. It to recreate not the cache by relationship a node, or term, but considers that an url = a page, that it is node or term or the other.

You can disable cache for any page or domain.tld...

Of it made, an url of the style: domain.tld > / term-raw / term-raw / nodetitleraw will be in cache under the shape
Dir ( domaine.tld ) = > Dir (term-raw) = > Dir (term-> raw) = > nodetitleraw.html

With boost, the modulates create has directory term, has directory node, ...

Sébastien

Grayside’s picture

Grayside commented

Best translation effort: Cache Static creates a cached version of a viewable page, Boost creates a cached version of page components. Also, Cache Static has a variety of administrative interfaces intended to provide fine-grained control for what pages are cached.

mikeytown2’s picture

mikeytown2 commented

Boost already has cache control, you can tell it not to cache certain pages; interface is the same as blocks. We are working on the administrative side of boost #326515: Roadmap For stable 6.x-1.0.

mikeytown2’s picture

mikeytown2 commented

@sebyoga
I am willing to work with you in terms of improving boost. The one thing your project has that we don't is a db table. In terms of administrative things, having a table sure makes life easy, and allows for some very fine grained control of the cache; all the things that make this project different from boost as far as I know.
#453426: Merge Cache Static into boost - Create GUI for database operations

mikeytown2’s picture

mikeytown2 commented
Title: consider merging with boost module or document diferences from it » Merge into Boost Complete.
Component: Code » Miscellaneous
Category: task » support
Status: Active » Needs review

Boost does everything this module does functionality wise. Can a notice be added to the top of this project stating this was an unsuccessful fork of the Boost module? Also if any functionality is missing, please let me know.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

@mikeytown - if sebgoya agrees then yes, that can be added. Otherwise you will have to follow the abandoned projects process to take over the project and mark it as abandoned.

sebyoga’s picture

sebyoga commented

Hello,
For the voucher of the community, I agree to enclose this module. For the reason that it is merged to the module Boost.

Thank you,
Best regards, Sébastien