On Fri, Jan 30, 2009 at 10:50 AM, John Beranek <john_at_redux.org.uk> wrote:
> I've been experimenting with the graphing functionality of Subclipse,
> and it's rather good, albeit a bit slow to build the cache.
I've actually been really happy with the performance. It is much
better than I thought it could be. Obviously my repositories could
just be a lot smaller than yours, but I only work on a slow DSL
connection full-time. Building the cache of Subversion's repository,
which is the biggest one I work with, is fast.
> This brought me to thinking that the same system on a server could be
> efficient and speedy for users.
> So, what do think the chances are of running the Subclipse graphing code
> on a server-side installation, abstracted from the rest of
> The cache would be global, and nodes could be rebuilt on a post-commit
> So, what do you think?
It really isn't a viable idea for a general purpose product. There
would just be too many pieces for someone to put in place to use it.
You need hook scripts to build the data, You need a server and some
kind of protocol to serve it to the client. If your repository is on
tigris or Google Code or sf.net how could you use this?
The only solution beyond caching is that we need Subversion itself to
grow this feature somewhat more natively. Basically, be able to ask
Subversion for this information and let it calculate the information
from its repository and provide it back. Until then, I think we are
stuck with custom caches.
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2009-01-30 17:04:46 CET