From: "Shawn O. Pearce" <spearce@spearce.org>
To: Farrukh Najmi <farrukh@wellfleetsoftware.com>
Cc: Kyle Moffett <kyle@moffetthome.net>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
git@vger.kernel.org
Subject: Re: Any overview available on jgit codebase?
Date: Sat, 15 Nov 2008 15:15:37 -0800 [thread overview]
Message-ID: <20081115231537.GD2932@spearce.org> (raw)
In-Reply-To: <491F2F5E.20206@wellfleetsoftware.com>
Farrukh Najmi <farrukh@wellfleetsoftware.com> wrote:
>
> At minimum could anyone tell me what packages and classes to look at in
> order to make changes to jgit so it uses a database instead of
> filesystem to references.
See RefDatabase, created by Repository. You would want to replace
RefDatabase with your own implementation, which means abstracting
that class to be an abstract base class or an interface.
RefUpdate and RefLogWriter are connected to RefDatabase, so you
would likely need to modify those too in order to make the change,
especially since RefUpdate is the "INSERT OR UPDATE OR DELETE"
logic. :)
BTW, I want to do that RefDatabase abstraction anyway, because I'd
like to get an in-memory only version of RefDatabase, to make unit
testing easier. So abstracting this code may be useful beyond just
your desire to back Git with a JDBC-style database.
--
Shawn.
next prev parent reply other threads:[~2008-11-15 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 19:59 Any plans to support JTA and XA in jgit? Robin Rosenberg
2008-11-13 20:27 ` Farrukh Najmi
2008-11-13 21:54 ` Robin Rosenberg
2008-11-14 14:38 ` Kyle Moffett
2008-11-14 14:45 ` Farrukh Najmi
2008-11-15 20:21 ` Any overview available on jgit codebase? Farrukh Najmi
2008-11-15 23:15 ` Shawn O. Pearce [this message]
2008-11-16 0:21 ` Farrukh Najmi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081115231537.GD2932@spearce.org \
--to=spearce@spearce.org \
--cc=farrukh@wellfleetsoftware.com \
--cc=git@vger.kernel.org \
--cc=kyle@moffetthome.net \
--cc=robin.rosenberg.lists@dewire.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox