OK.Thanks
On Fri, Feb 4, 2011 at 8:53 PM, John McCaffrey john.mccaff...@gmail.comwrote:
i think this is something for the integrity forum, as not many people here
have tried it. (and the issues we're having are not standard rails app
issues).
Let me know if you get an answer from the
You could go beyond normal rails caching and manually use Redis to nail the
DB problems as well - each time new data is requested Marshal dump the
results into Redis, then do a failover query of Redis before hitting AR for
each query. You could probably serve that volume of requests with simply
Amazon has now removed the email address verification requirement of the
Reply-To header. Sweet!
On Fri, Feb 4, 2011 at 12:53 PM, Dan Croak dcr...@thoughtbot.com wrote:
The only problem we've seen so far is not being able to use the Reply-To
header because THAT email address must be verified:
Is it possible to supply custom VCL code for your heroku application
that will change the way varnish behaves in front of it? Being able to
change how the cache hash is generated (for instance using information
in cookies as well) could be really useful.
--
You received this message because you
