Re: libefs and file types




> 1.  I'm not convinced we should use libefs.  If we do, then I would
>     probably put it in the beginning of the file.  Microsoft
>     effectively just writes it out at the beginning of the file;
>     the client calls IPersistStream::GetClassID(), writes it out to
>     the stream, and then writes the PersistStream out using
>     IPersistStream::Save().

Good point.  Because currently, we would have no way of
differentiating a .efs file containing different "toplevel" files.

> 2.  We are going to migrate to OAF eventually.  Maybe OAF makes this
>     easier for us?

Dont think this has anything to do with the problem.

miguel.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]