Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » U++ Core » Optional serialization techniques
Re: Optional serialization techniques [message #31371 is a reply to message #31368] Fri, 25 February 2011 19:42 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14267
Registered: November 2005
Ultimate Member
Mindtraveller wrote on Fri, 25 February 2011 09:34

Thanks everyone for the answers. I guess the problem is solved.

mirek wrote on Fri, 25 February 2011 11:46

That said, it does not solve the problem all the time and generally, I would NOT recommend using binary serialization for permanent storage of important files. It is fine for configs (where if you loose one, it is not that bad) or for transfering data (e.g. over network).
Do not use it for documents Smile

BTW, why? Looks like not a bad storage solution.


I guess the main problem is that it is so simple to serialize things that it is too easy to accidentally break the format...

And, sometimes, the problem also is that it is impossible or too diffuclt to keep backward compatibility. Simple example would be forgetting to put 'version' somewhere...

Mirek
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: do upp have an equivalent of "eval()" in Javascript
Next Topic: Core/Path.cpp: the limitation of GetCurrentDirectory for POSIX
Goto Forum:
  


Current Time: Tue Aug 26 06:16:32 CEST 2025

Total time taken to generate the page: 0.05274 seconds