From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Nigel Magnay <nigel.magnay@gmail.com>
Cc: Git ML <git@vger.kernel.org>, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH JGIT] Minor : Make ObjectId, RemoteConfig Serializable
Date: Sun, 8 Feb 2009 03:13:21 +0100 [thread overview]
Message-ID: <200902080313.21785.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <320075ff0902061315g3f8b9c9bj92f528e700d59c50@mail.gmail.com>
fredag 06 februari 2009 22:15:29 skrev Nigel Magnay:
> Make AnyObjectId and RemoteConfig Serializable.
> When using jgit as a library in other tools, it's helpful to be able
> to use the nice, tested bits of jgit rather than String, but need to
> be able to serialize them.
A problem (big problem) with serialization is that it often leads to
fragile interfaces. One might want to have precise control over
the serialization so a change in the implementation doesn't affect
compatibility. Serializing AnyObjectId should not depend on the
implementation de jour. Second, how do we handle subclasses?
But maybe leaving it this way would be our way of saying that
the interface may break at any time, promise.
-- robin
next prev parent reply other threads:[~2009-02-08 2:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <320075ff0902060702n7573aaecu9054626ee9a6991@mail.gmail.com>
2009-02-06 21:15 ` [PATCH JGIT] Minor : Make ObjectId, RemoteConfig Serializable Nigel Magnay
2009-02-08 2:13 ` Robin Rosenberg [this message]
2009-02-08 13:26 ` Nigel Magnay
2009-02-08 19:10 ` Shawn O. Pearce
2009-02-08 19:45 ` Robin Rosenberg
2009-02-08 19:47 ` Shawn O. Pearce
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=200902080313.21785.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=nigel.magnay@gmail.com \
--cc=spearce@spearce.org \
/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;
as well as URLs for NNTP newsgroup(s).