BundleArchive State Files

[Felix Meschberger <Fe...@day.com>]

Hi,

I just attached a patch to [FELIX-31] to persist the value of the last
modification time stamp. According to my understanding the value of
the last modification time of a bundle should be persisted like for
example the start level or the state.

While working on this I started wondering whether it would make sense
to combine all those state files in a bundle archive into a single
file - for example a properties file. This would in my opinion make
handling of the persisted information easier as the file needs only be
loaded once.

If there would be interested in combining this information, I could
file an issue and provide a patch.

Regards
Felix

Re: BundleArchive State Files

[Felix Meschberger <Fe...@day.com>]

Hi,

Ok, lets just drop the idea again :-)

Regards
Felix

On 9/22/06, Richard S. Hall <he...@ungoverned.org> wrote:
> Felix Meschberger wrote:
> > I just attached a patch to [FELIX-31] to persist the value of the last
> > modification time stamp. According to my understanding the value of
> > the last modification time of a bundle should be persisted like for
> > example the start level or the state.
>
> Thanks. I will apply this shortly.
>
> > While working on this I started wondering whether it would make sense
> > to combine all those state files in a bundle archive into a single
> > file - for example a properties file. This would in my opinion make
> > handling of the persisted information easier as the file needs only be
> > loaded once.
>
> If they are in a single file, then this means that they all also have to
> be written to disc each time there is a change too. Some properties,
> like location, are never written again since they never change. Not a
> super big deal, but I doubt that it is a big deal that they are read
> independently either. One of the main goals of the bundle cache was to
> be simple. That is also why everything is stored as plain ASCII so that
> it is easily readable and editable (if need be).
>
> > If there would be interested in combining this information, I could
> > file an issue and provide a patch.
>
> I am not against it, but at the same time it doesn't really seem like an
> imperative change, unless we have some evidence suggesting otherwise.
>
> -> richard
>

Re: BundleArchive State Files

["Richard S. Hall" <he...@ungoverned.org>]

Felix Meschberger wrote:
> I just attached a patch to [FELIX-31] to persist the value of the last
> modification time stamp. According to my understanding the value of
> the last modification time of a bundle should be persisted like for
> example the start level or the state.

Thanks. I will apply this shortly.

> While working on this I started wondering whether it would make sense
> to combine all those state files in a bundle archive into a single
> file - for example a properties file. This would in my opinion make
> handling of the persisted information easier as the file needs only be
> loaded once.

If they are in a single file, then this means that they all also have to 
be written to disc each time there is a change too. Some properties, 
like location, are never written again since they never change. Not a 
super big deal, but I doubt that it is a big deal that they are read 
independently either. One of the main goals of the bundle cache was to 
be simple. That is also why everything is stored as plain ASCII so that 
it is easily readable and editable (if need be).

> If there would be interested in combining this information, I could
> file an issue and provide a patch.

I am not against it, but at the same time it doesn't really seem like an 
imperative change, unless we have some evidence suggesting otherwise.

-> richard