On Mon, Nov 2, 2009 at 3:20 PM, David Anderson <[email protected]> wrote: <snip> > However, to our mind download deletion was intended to provide a means > for users to stop serving content that should not be online (say you > mistakenly uploaded a broken archive, or an installer infiltrated with > a malware payload). In that use case, it still makes sense to serve > with HTTP caching, since the only distinction we need to make is > between the canonical content of the URL and 404. > > Unfortunately, the deletion feature has been used mostly to change the > content of an URL, which is a bad practice for a couple of reasons > (unpredictability for users being the biggest). The caching we apply > breaks this use case. And that sucks, because HTTP caching is > generally rather awesome for various reasons. > > That said, yes, given how people use our featureset today, we need to > revise our caching policies. We're looking into how to do this while > preserving some of the niceties that HTTP caching gives us.
It's a quite common for projects to provide nightly builds of their open source projects, I would like to do this as well, but have not found an easy way to do this. It would basically mean uploading radegast-nightly.zip & installer with the same file name over and over again. What is the recommended way do accomplish this for a project hosted at Google code? Latif --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
