Re: Request: Test suite for EFS.
- From: Hans Erik Martino Hansen <martino daimi au dk>
- To: Daniel Veillard <Daniel Veillard w3 org>
- Cc: Miguel de Icaza <miguel gnu org>, nat helixcode com, gnome-components-list gnome org, gnome-list gnome org
- Subject: Re: Request: Test suite for EFS.
- Date: Thu, 17 Feb 2000 18:29:06 +0100
On Wed, Feb 16, 2000 at 08:21:45PM +0100, Daniel Veillard wrote:
> On Wed, Feb 16, 2000 at 08:05:44AM -0600, Miguel de Icaza wrote:
> >
> > > This is obviously pseudo-code and not usable directly. But the main
> > > problem that it brings up is getting the MIME type of the embedded
> > > streams. I think we have to add a get_mime_type() method to
> > > PersistStream. We at least need to be able to detect if the stream is
> > > going to send us back XML, so that we can just drop it in-place
> > > instead of base64 encoding it, or whatever.
> >
> > The fact that OLE2 just stores the class id in the stream happens to
> > be a nice side effect. The stream can be anything (XML binary, SS).
> >
> > But XML still does not provide a file-system-inside-a-file
> > abstraction, or if it does, it does it in the most inneficiently mode
> > that someone could think of.
> >
> > XML might be cute, but how does an image look in XML? Not very
> > XML-ish if you ask me. It looks base64-ish to me.
>
> depends on the image format of course ! SVG and a couple of other
> format just looks nice in XML ...
>From a users point of view I think it is important that a document is
stored in one file, if not, there would be some problems
* how would you know which file is the root document
* how would you know which files belongs to the document
* how are the unneeded components `garbage collected'
However there are benefits of storing the components one by one.
* if there are many large components it may be slow to save after a
small change, an example would be a large high resolution DTP
document
A solution would be to design EFS so that it is transparent if the
true file system is used or the EFS is used.
I didn't quite get why the EFS should be anti-XML, if you can have
href's to components inside the EFS.
/erik "If you have a hammer, everything looks like a nail"
--
\|/ ____ \|/ Erik M. Hansen <martino@daimi.au.dk>
"@'/ oo \`@" http://www.daimi.au.dk/~martino/
/_| \__/ |_\ "Der er nu 317 dage, 6 timer
\__U_/ og 58 minutter tilbage i dette årtusind"
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]