Re: review of the Storage interface



Michael Meeks wrote:

> I am extremely concerned that your suggestions are extensive and I
> do not understand why many of them are neccessary. What application do you
> have in mind for eg. locking, content types on storages etc. etc. Why are
> these neccessary to your mind ? MS manage to cope without this
> functionality and the interface is currently nice and thin. It would be
> good if you could try and rationalize each one on the list carefuly before
> writing any code.

Microsoft supports a SetClass method (I think so), where you can set the
content_type
of the storage. This identifies the code associated with the contents of
the storage, which seems to be useful (you simply know what is contained
in the storage). You can also get the type of a storage or stream with the
Stat method. Consider the case where a word document contains a excel sheet.
If I know the content type of the storage containing the excel sheet I can
extract it with (only as example) the file manager.

-------------

There are some advantages if we restrict ourselves setting the type of  a
stream/storage to the point in time when the stream/storage is created
- but only if we save to a storage which we can't access randomly.
(make only sense with my previous sequential storage suggestion).

    Dietmar









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