Use of versioning in archiving.

[Gerrit Van Dyk]

Hi all,

I logged a bug yesterday in connection with the unarchiving of NSValue.
Thanks Richard for responding so quickly. I was just wondering now, I saw
that the encoding of NSValue also changed without using versioning. Is this
a common practice within GNUstep to change some of the encoding methods
without checking for versioning? Our system makes use of Blob's in the
database, these blobs are created using archiving and then unarchived when
their details are needed. If GNUstep does not check for versioning then our
blobs will become unusable the moment the archiving methods change. Should I
start using different ways of archiving our objects into blobs, just to make
sure that our system will not become unstable with a new release of GNUstep.
I can also see a potential problem over DO if the versions of GNUstep on
either side of the connection is not 100% the same.

Regards
Gerrit van Dyk
 
-------------------------------------------------------------------------
This e-mail is intended only for the use of the individual or entity named
above and may contain information that is confidential and privileged,
proprietary to the company and protected by law. If you are not the intended
recipient, you are hereby notified that any dissemination, distribution or
copying of this e-mail is strictly prohibited. Opinions, conclusions and
other information in this message that do not relate to the official
business of our company shall be understood as neither given nor endorsed by
it.