Hello, your module seems to be duplicate with mine and catch's one, see:
http://drupal.org/project/core_library
http://drupal.org/project/agrcache

We should definitively merge. We also already opened a core issue for D8 better aggregation system, see #1014086: Stampedes and cold cache performance issues with css/js aggregation

Comments

catch’s picture

Subscribing, came here to post the same thing.

mikeytown2’s picture

This is for D6; how do you propose merging?

Also I've built in some stats on how often a file changes so that smarter bundles can automatically be generated.

mikeytown2’s picture

This project is getting closer to completion. Check the README.txt file and give the code a spin. Also if you know of any CSS/JS bug fixes that should get into 6.x, point me towards the issue queue.

catch’s picture

I thought I'd replied to #2 but looked back here and that apparently didn't go through.

We haven't managed to merge core_library and agrcache yet, but it'd be good to combine efforts where possible since all three of us appear to agree on what the problems are, if not necessarily all the solutions.

Seems like you're focused on Drupal 6 at the moment. I'd considered backporting agrcache back to D6 at some point, but likely won't do that now that this module exists. If you get to a point where you're thinking of porting this to D7, it'd be good to talk about how we could co-ordinate so we can avoid three different modules that do similar things.

I have a core patch for the imagecache generation now at #1014086: Stampedes and cold cache performance issues with css/js aggregation - assuming that can get into D8 and backported into D7, then agrcache would be obsolete and I'd happily retire it.

What I've love us to get to is the ability to swap out the file grouping method, and swap out the actual css/js processing/minification separately - ideally get that into Drupal 8, have a contrib module for 6 and 7 that just provides the API to change those implementations, then the different approaches to both grouping and js minification/css parsing could just use that and be interchanged without needing the same boilerplate code. They might live in the same project, but they wouldn't need to.

I've also updated #1048316: [meta] CSS and Javascript aggregation improvement with more thoughts on this in general.

Vacilando’s picture

I absolutely agree with the general point of not duplicating efforts. However, from my point of view, I am most interested in advagg, because there is no other such module for D6 developed, and because advagg is developed and shaping up extremely quickly. If there is a joint solution, I would hope that it will not slow down the excellent progress I've seen around this module. I also note that at the moment this appears to be the most used module out of the three similar ones.

mikeytown2’s picture

Next up will be one to many functionality. What that means is one aggregate could spit out multiple files. I see my own implementation of bundle cache doing this as well as CSS Embedded Images - #1078060: CSS Embedded Images - Add in support for advagg's hooks. I will release an alpha version of advagg before going down this road so there is a "stable" release available.

This means I need to roll a patch for this module as well: Stage File Proxy #1078218: support for any menu link in the files directory

Long story short; I'm far from considering merging the projects together as the underlying structure of this module will most likely change in the near future.

mikeytown2’s picture

one to many functionality is done; still ironing out some issues but the first official release might be a beta at this point.

mikeytown2’s picture

Status: Active » Closed (won't fix)

Going to won't fix this