Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
Storage API (http://drupal.org/project/storage_api) seems to be doing good work on automatic synchronization, deduplication, etc. without using a daemon.
Is there a possibility to use that module, or add similar functionality in CDN integration, for people who cannot install the Python daemon on their servers (e.g. on shared servers or on clouds like Mosso/RackspaceCloud). I am sure a PHP system would take a bit longer to synchronize than the dedicated Python daemon, but at the same time it would allow great many more users to enjoy the advanced mode of CDN intergration.
Comments
Comment #1
chrism2671 CreditAttribution: chrism2671 commentedDid you try this out, by any chance? It appears to offer similar functionality to the CDN integration module, with reduced complexity, so I'd be keen to know if you gave it a shot.
Comment #2
Vacilando CreditAttribution: Vacilando commented@chrism2671, no, I did not try Storage API. I think the following sentences from the project page put me off: "At the moment, it can only be used by modules that utilise it directly, e.g. Blue Droplet Video. With Drupal 7 it will be possible for Drupal core to utilise Storage API directly." Guess it should be tried though.
Comment #3
chrism2671 CreditAttribution: chrism2671 commentedYes, I did try it and slightly missed the point. It provides the backend part of transferring things to S3, but only when another module (yet to be written) instructs it do so.
In other words, it's a very good idea and a well written API but it still lacks the key functionality that we're looking for on this thread.
Comment #4
Wim LeersI'll be talking to jbrown during the DrupalCon here in Copenhagen to find out whether it's feasible to also support his Storage API in the CDN integration module.
From just looking at the project page, it already looks very promising in any case :)
Comment #5
Wim LeersI just contacted Jonathan Brown (jbrown), the maintainer of the Storage API module to sit down and discuss the possibilities. I'll keep you posted!
Comment #6
Wim LeersI talked to Jonathan Brown about an hour ago. He explained how he had been working on Storage API, how it evolved and where it's going.
Basically, the Drupal 6 version is flawed in many ways, although it's used by quite a few sites (a couple of hundred) for his Bluedroplet video solution. He has indicated that we should focus on the Drupal 7 version instead: it's much better and is the only one that will receive enough attention to make it rock solid.
So, unfortunately, this feature won't be implemented won't be implemented for the Drupal 6 version of this module, but it's extremely likely that it will be supported in Drupal 7!
Comment #7
Vacilando CreditAttribution: Vacilando commented:-(
Comment #8
jan_v CreditAttribution: jan_v commentedThat's too bad. Could really use it in 6.x .
I'm looking forward to seeing CDN module and storage_API perform in D7.
Comment #9
Wim LeersFile Conveyor is too prohibitive for most users to install.
It's also very hard to gain contributions from Drupal users for something that's not written in PHP/Drupal.
And lastly but not least, there's now only one major CDN left that only supports Push and not Origin Pull: Rackspace Cloud Files (CloudFront supports Origin Pull since November 9, 2010, see the relevant issue #968614: Link to Amazon CloudFront custom origin docs.
So, the only major benefit of File Conveyor that's left (it's no longer needed for pushing, and Origin Pull offers little opportunity for CDN provider lock-in), is its ability to process files before they get sent to the CDN; i.e. CSS and JS minification, and image optimization.
However, CSS minification is built in in core, GZIPping is possible with a simple Drupal module (CSS Gzip). JS minification is possible with another simple Drupal module (Javascript Aggregator). Both of these modules have already been made compatible with CDN module version 2.
The BundleCache module also supports an even more advanced way for optimizing CSS and JS. Compatibility with that module is still being worked on (see #401508: Document how to use BundleCache with CDN.
So that only leaves us with the necessity to be able to optimize images as a frequent use case that's not yet supported from within Drupal (for more advanced use cases, you should continue to use File Conveyor). BundleCache already has preliminary support for processing images (it can serve them from a different host), but it still needs a lot of work to actually optimize them losslessly.
So, my plan is to work on adding support for optimizing images from within BundleCache. Using the CDN and BundleCache modules (when the latter is ready) will bring most possible Web Performance Optimizations to your Drupal site.
Comment #10
Wim LeersSister issue in the Storage API issue queue: #1429184: Storage API module + CDN module.
Comment #11
Wim LeersWon't happen for 7.x, might happen for 6.x.
Comment #12
jpstrikesback CreditAttribution: jpstrikesback commentedYou've changed the issue to 7.x but said it might happen for 6.x? Late night/Intentional? :)
Cheers,
JP
Comment #13
Wim LeersStorage API's project page says:
That's why I don't see it happening for D6.
Comment #14
jpstrikesback CreditAttribution: jpstrikesback commentedRight but
confused me : )
Comment #15
jpstrikesback CreditAttribution: jpstrikesback commentedEither way, really interested in what goes on here
Comment #16
Wim Leers#14: LOL, those should've been the other way around :) My apologies!
In general: this is far more likely to happen if you help build it… ;) :)
Comment #17
jpstrikesback CreditAttribution: jpstrikesback commentedHopefully I can even if it's a small contribution...I'm getting my feet wet now and trying to find some kind of documentation on implementing the Storage API
Comment #18
Wim Leers#712998: CDN + Media Mover 2.x integration moved into the Media Mover issue queue, because nothing seems to be happening there.
Comment #19
rogical CreditAttribution: rogical commentedThis could be a 3rd module.
I suppose this would be the perfect solution in the future.
Storage api provides redundancy and scalability, CDN provides load balancing!
Comment #20
gunwald CreditAttribution: gunwald commentedSubscribing.
Comment #21
ianthomas_ukTo subscribe to an issue please click the green 'follow' button on the right of the issue summary. This avoids filling the comments with 'subscribe' messages.
Comment #22
thijsvdanker CreditAttribution: thijsvdanker commentedDid anyone get anywhere with this? @jpstrikesback what did you see?
Comment #23
Wim Leershttps://www.drupal.org/project/storage_api hasn't really gone anywhere during the Drupal 7 cycle. Anybody is free to write a
cdn_storage_api
integration module.