[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: JavaHL: Serializable and breaking binary compatibility?

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-04-23 23:34:19 CEST

On 4/23/07, Blair Zajac <blair@orcaware.com> wrote:
> I needed to serialize a Revision and discovered that the class doesn't
> implement java.io.Serializable.
> I have a patch ready that serialized this class and any other class that
> doesn't include native methods and just acts like a C structure for data.
> ChangePath
> CommitItem
> CopySource
> DirEntry
> Info
> Info2
> Lock
> MergeInfo
> ProgressEvent
> Revision
> RevisionRange
> Status
> Will this break Java code that compiled against the old,
> non-serializable classes?

No. The only thing that would break old clients is removing methods
that used to exist or making them work differently. Making classes
Serializable will not do that.

> Thoughts?

My only concern is maintaining it properly. Handling serializing old
versions etc. OTOH, we probably do not change data elements very
often, so it is not likely too big of a deal.

Mark Phippard
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 23 23:34:27 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.