From owner-freebsd-hackers@FreeBSD.ORG Sat Mar 22 01:11:15 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D1A44106566C for ; Sat, 22 Mar 2008 01:11:15 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id A1AC48FC15 for ; Sat, 22 Mar 2008 01:11:15 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.128] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id m2M1Aupb058433; Fri, 21 Mar 2008 18:10:56 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <47E45CA0.5000705@freebsd.org> Date: Fri, 21 Mar 2008 18:10:56 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: d@delphij.net References: <47E4405E.2080609@delphij.net> <874pazpqjq.fsf@kobe.laptop> <47E45984.3080907@delphij.net> In-Reply-To: <47E45984.3080907@delphij.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Giorgos Keramidas , freebsd-hackers@freebsd.org Subject: Re: Some versioned storage program? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Mar 2008 01:11:16 -0000 Xin LI wrote: > Ah... Ok I think I should have mentioned the purpose of the system. It > is supposed to be used in a CMS system, and the storage program will be > used as one auxiliary backend where rendered pages are being stored. I've considered using SVN+Apache behind one or more Squid caches for serving pages: * Easy remote update (via SVN command-line or other tools; TortoiseSVN even makes manual updates easy for most Windows users). * Easy tracking and rollback. * No need to mess with explicit "export" processes; simply committing the change to SVN makes it available. Not sure if this suits your needs or not, but I thought I'd throw the idea out there. Cheers, Tim Kientzle