Matt Good kirjoitti: > On Oct 23, 1:27 am, Jani Tiainen <[EMAIL PROTECTED]> wrote: >> I was just wondering has any dev investigated possibility to use pySVN >> as a backend for remote repositories? >> >> It seems to be in pretty good shape nowadays. >> >> Is there be some drawbacks/compatibility problems that prevents using >> it? Or does it just need someone to write such a backend plugin that >> uses pySVN? > > Speed is going to be a drawback since browsing files and diffs will > require Trac to pull the entire file from the remote server each time > and then transmit it back to the user. > > Svnsync works to mirror the repository so that accesses are local and > it only needs to do incremental updates of the mirror.
Very good point. Wonder how it works with tortoissvn (or plain svn) since now I only have HTTP access to our repositories (except for trac that has been granted direct file access). Wouldn't it get performace hit too from my HTTP access? (Or is it due the fact that usually (tortoise)svn works with repository checkout that contains base version so you can do certain stuff without hitting repository at all... Given a look, pySVN is not very good for Trac purposes (too highlevel so to say). So I'll either manage without it or take a look on that svn_ra stuff that already exists at some form. Alas. Well, I know there exists more useful plugins to be made... -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
