From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Nigel Magnay <nigel.magnay@gmail.com>, Git ML <git@vger.kernel.org>
Subject: Re: [JGIT PATCH] 1/2 : (reworked) Externalizable/Serializable Items
Date: Wed, 18 Feb 2009 15:27:45 -0800 [thread overview]
Message-ID: <20090218232745.GP22848@spearce.org> (raw)
In-Reply-To: <200902190021.33382.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
> onsdag 18 februari 2009 22:48:59 skrev "Shawn O. Pearce" <spearce@spearce.org>:
> >
> > Non-Java reading a Java serialization stream? Seriously?
>
> No, that was my objection to using writeObject, as that make
> it a Java-only stream, but then it might not be worth doing
> it via the serialization mechanism.
IMHO, if we are talking about either java.io.Serializable or
java.io.Externalizable, there's no point in considering a non
Java peer.
If you want a non-Java format, we'd need to consider a much
more neutral encoding, like Google's protobuf, or *shudder*
XML/JSON, or cooking up our own format.
That wasn't this thread started with. The original poster just
wanted an easy way to serialize some basic data types from JGit,
as part of some higher level stream being done in the container
application. Since that higher level stream is a apparently a
Java object serialization stream, we just need to match that.
--
Shawn.
next prev parent reply other threads:[~2009-02-18 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 20:12 [JGIT PATCH] 1/2 : (reworked) Externalizable/Serializable Items Nigel Magnay
2009-02-16 20:16 ` Johannes Schindelin
2009-02-18 16:30 ` Shawn O. Pearce
2009-02-18 20:59 ` Robin Rosenberg
2009-02-18 21:48 ` Shawn O. Pearce
2009-02-18 22:19 ` Sverre Rabbelier
2009-02-18 23:21 ` Robin Rosenberg
2009-02-18 23:27 ` Shawn O. Pearce [this message]
[not found] ` <320075ff0902200127m3e516621m60a608bc891ab992@mail.gmail.com>
2009-02-20 9:28 ` Nigel Magnay
2009-02-20 20:32 ` 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=20090218232745.GP22848@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=nigel.magnay@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).