vB Optimise Pro 2.3.0 Update

We turned expired headers off due to them caching a little too much - so we've began CDN Integration with vB Optimise, you'll notice a lot of static content here on DBT is being delivered from a Rackspace Cloud CDN now thanks to vB Optimise v3 which is in experimental/beta stages.

Sweet - can't wait to try this out. Has anything been figured out with avatars or attachments?
 
Sweet - can't wait to try this out. Has anything been figured out with avatars or attachments?

Avatars under the filesystem are public anyway so they could be put on a CDN, but neither them or avatars have yet - the first beta is working with integration and automatically uploading/sync'ing content to the cloud. Right now I've only dabbled with the RS Cloud API, I'll be checking out amazon too and maybe another - other than that the CDN feature will strictly be limited to bridge-apis I (or others) create for it.

I can tell you that private attachments will never go on a CDN, because a CDN is public :p
 
What if the attachment URL was not a direct link, but a redirect to the CDN url? I realize if someone gets the CDN url they can just download at will.

Might help you save resources, but it would still make private attachments public which would be a bad thing even as an option really.
 
@tavenger5: While true- A user could post the link publically, and for some forums that just wouldn't be acceptable - but it isn't dead in the water as I probably won't be introducing user content CDN (avatars, signatures, uploads) until an update after vBO v3 which will focus on soely on the websites generic content, which includes images used on pages from the styles, misc images like thread/post icons, smilies and clientscript files (javascript/css).

Additionally CDNs work with a TTL ("Time To Live") which may hinder things like attachments, vBO can update a file on the cdn but people won't received the updated file until the TTL has expired which can anything (you'd control that through your CDN provider), typically though a CDN TTL is approx 72 hours.

@Maximilian2: Not really, we can't control anything on the CDN side of things - we can just pass you to the URL which at that point can be publically distributed with ease.
 
Yeh, I think regular static image files, css, and javascript are the most important things to throw on a CDN.

Speaking of CSS and Javascript - any chance that the CSS files can be minified? How about combining and compressing (through google closure compiler) JS files?
 
Yeh, I think regular static image files, css, and javascript are the most important things to throw on a CDN.

Speaking of CSS and Javascript - any chance that the CSS files can be minified? How about combining and compressing (through google closure compiler) JS files?

If this is done, please offer a non-minified version for download as well.
 
Minifying is one option, though last on my mind. As for combining css/js files that'll likely be a no-no, it causes too many things to break really and once cached in your browser you don't need to download them again and again so it doesn't provide much advantage (especially since they'll be off your main server anyway).
 
Back
Top