git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [JGIT PATCH] 1/2 : (reworked) Externalizable/Serializable Items

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 18, 2009, 23:27 UTC
Message-ID
<20090218232745.GP22848@spearce.org>
In-Reply-To
<200902190021.33382.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
Show 7 quoted lines
> 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.
Previous: Robin RosenbergNext: Nigel Magnay
Message 8 of 10 in “1/2 : (reworked) Externalizable/Serializable Items”
  1. 1/2 : (reworked) Externalizable/Serializable ItemsNigel Magnay, Feb 16, 2009
  2. Johannes SchindelinFeb 16, 2009
  3. Shawn O. PearceFeb 18, 2009
  4. Robin RosenbergFeb 18, 2009
  5. Shawn O. PearceFeb 18, 2009
  6. Sverre RabbelierFeb 18, 2009
  7. Robin RosenbergFeb 18, 2009
  8. Shawn O. PearceFeb 18, 2009
  9. Nigel MagnayFeb 20, 2009
  10. Shawn O. PearceFeb 20, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.