Re: version control/change history plugin?

On Thu, 3 Aug 2006, Ryan Barrett wrote:
>
> good call. i like this, since it lets pyblosxom and cvs/svn each do what 
> they do best. even better, a few people have discussed it, and an svn 
> pyblosxom plugin (minus history and diffs) already exists:
>
> http://www.baus.net/svnpyblosxom
>
> (discussion at http://mg.pov.lt/blog/pyblosxom-setup.html and 
> http://cubiclemuses.com/cm/blog/less_blog.html .)
>
> the main problem is resources and latency. you have to spawn an svn 
> process for every request, since svn is the source of the original post 
> creation date. that's both expensive and very slow.
> 
> christopher baus' plugin solves this by using a dedicated cache process, 
> memcached. it sounds like it works, but it's really heavyweight, and not 
> an option for pyblosxom installations on shared hosting plans (ie most 
> of them).

What makes you say that most PyBlosxom installations are on shared hosting 
plans?  Did you do a study, read about this in a study, or are you drawing 
on experience?


> i haven't looked at the other date-preserving plugins, but one of them 
> might work instead. then you'd only need to run the svn client on diff 
> and history requests. still far from ideal, though.
>
> thoughts?

If you don't like the idea of having a process maintain the cache, then 
persisting it to disk is probably the way to go.  There are several 
plugins that do this sort of thing in the registry.  I use flixq which I 
think does this.

Hope that helps--
/will

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV