{"thread":{"id":"6177","subject":"Gitweb - caching","startedAt":"2006-12-31T10:30:14Z","lastAt":"2006-12-31T20:52:11Z","messageCount":4,"participants":["J.H.","Robert Fitzsimons","Jeff Garzik","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"30574","messageId":"45979136.3070901@eaglescrag.net","threadId":"6177","inReplyTo":null,"subject":"Gitweb - caching","fromName":"J.H.","fromEmail":"warthog19@eaglescrag.net","sentAt":"2006-12-31T10:30:14Z","receivedAt":"2006-12-31T10:30:14Z","isPatch":false,"sender":{"key":"warthog19@eaglescrag.net","avatar":null},"body":"There has been some recent discussion concerning the amount of resources\nthat gitweb is chewing through, particularly on kernel.org.  I've just\npushed a small set of changes out to kernel.org that add in caching to\nthe gitweb thats running on it.  Changes are published at\ngit://git.kernel.org/pub/scm/git/warthog9/gitweb.git\n\nThoughts or comments are welcome.\n\n- John 'Warthog9'\n"},{"id":"30585","messageId":"20061231174123.GI6558@localhost","threadId":"6177","inReplyTo":"45979136.3070901@eaglescrag.net","subject":"Re: Gitweb - caching","fromName":"Robert Fitzsimons","fromEmail":"robfitz@273k.net","sentAt":"2006-12-31T17:41:23Z","receivedAt":"2006-12-31T17:41:23Z","isPatch":false,"sender":{"key":"robfitz@273k.net","avatar":null},"body":"> Thoughts or comments are welcome.\n\nInteresting work, John.  Some initial comments:\n\n* It's a very intrusive set of changes.\n* An infinite expiry date isn't valid for all pages.\n* The other HTTP headers can change depending on the page returned.\n* A single cache directory is going to have problems as the number of\n  cached files grows.\n\nWhat are the benefits of doing this inside of gitweb instead of using\nsomething like mod_cache or mod_perl handlers?\n\nRobert\n"},{"id":"30590","messageId":"4598171D.2040002@garzik.org","threadId":"6177","inReplyTo":"20061231174123.GI6558@localhost","subject":"Re: Gitweb - caching","fromName":"Jeff Garzik","fromEmail":"jeff@garzik.org","sentAt":"2006-12-31T20:01:33Z","receivedAt":"2006-12-31T20:01:33Z","isPatch":false,"sender":{"key":"jeff@garzik.org","avatar":null},"body":"Robert Fitzsimons wrote:\n>> Thoughts or comments are welcome.\n> \n> Interesting work, John.  Some initial comments:\n> \n> * It's a very intrusive set of changes.\n> * An infinite expiry date isn't valid for all pages.\n> * The other HTTP headers can change depending on the page returned.\n> * A single cache directory is going to have problems as the number of\n>   cached files grows.\n> \n> What are the benefits of doing this inside of gitweb instead of using\n> something like mod_cache or mod_perl handlers?\n\nOr wrapping the gitweb output inside cgicache:\nhttp://linux.yyz.us/projects.html\n\n\tJeff\n"},{"id":"30591","messageId":"en97tp$kc1$1@sea.gmane.org","threadId":"6177","inReplyTo":"20061231174123.GI6558@localhost","subject":"Re: Gitweb - caching","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-12-31T20:52:11Z","receivedAt":"2006-12-31T20:52:11Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Robert Fitzsimons wrote:\n\n> * An infinite expiry date isn't valid for all pages.\n\nAn infinite expiry date is not valid at all. IIRC HTTP defines that\n\"infinite\" expiry is one year.\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"}]}