version control system (was mission critical apps)

[Wouter]

On 10 Feb 2004, at 20:20, use-revolution-request at lists.runrev.com wrote:

>
> Message: 2
> Date: Tue, 10 Feb 2004 18:12:32 +0000
> From: revolution at knowledgeworks.plus.com
> Subject: Re: version control system (was mission critical apps)
> To: How to use Revolution <use-revolution at lists.runrev.com>
> Message-ID:
> 	<OFEFB93489.5B23C271-ON80256E36.00606DAE 
> -80256E36.00640698 at knowledgeworks.plus.com>
>

snip

>
> I'm sorry Wouter, but I don't understand your question.  Could you
> elaborate?
>
> My idea is that all the components of a stack would be converted to  
> XML so
> that e.g. grepping/formatting/XML tools could be used to  
> edit/manipulate
> the components outside of Rev.  Moreover, the components should be  
> able to
> be selectively re-applied from the VCS e.g. you could go to the VCS and
> browse to a version of a stack from last week, find the component, and
> revert to the code for that component.
>
> Indeed, as more and more data sources are exposing XML interfaces, I'm  
> as
> interested in the principle of being to generate stacks from XML as I  
> am
> in saving stacks as XML.
>
> Bernard


Hello Bernard,
The principle of dissecting stacks into xml and resuscitating them from  
xml
is indeed very interesting.
But stack files are already an optimized kind of document. So I was  
wondering
which would be a more efficient way of archiving stacks, xml-files or  
storing
the binary data in custom properties?
Anyway opening stacks from binary data stored in custom properties is
much faster than reconstructing them from xml.

WA