| From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
|---|---|
| To: | Joel Miller <joelwmiller(at)sbcglobal(dot)net> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [SUGGESTION] CVSync |
| Date: | 2006-03-25 04:46:23 |
| Message-ID: | 20060325004600.G4637@ganymede.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 24 Mar 2006, Joel Miller wrote:
> Joshua D. Drake wrote:
>
>> Is there any reason why we don't allow rsync access to the cvs repo?
>>
> The only reason I can possibly think of is server load, comparing the
> timestamps for every file and directory in a repository for every rsync
> session could be taxing if everyone under the sun and all their cousins could
> do it.
>
> CVSync, on the other hand, can cache those timestamps into a file and send it
> to the client, offloading the comparison workload from the server to the
> client where it belongs.
I'm going to look at installing this also ... what does the client side
need?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-03-25 05:16:35 | Re: [SUGGESTION] CVSync |
| Previous Message | Marc G. Fournier | 2006-03-25 04:45:37 | Re: [SUGGESTION] CVSync |