FreeLists / openbeos / [openbeos] Re: kernel mime_table module

["François Revol" <revol@xxxxxxx>]

> 
> On 2005-01-06 at 07:02:58 [+0100], François Revol wrote:
> > > 
> > > > I would chose BNodeInfo as a starting point, as this class is 
> > > > the
> > > > one
> > > > that abstracts the file type stuff from the implementation.
> > > 
> > > Well, the `abstraction' is very direct. The properties it can get
> > > /set
> > > are
> > > directly stored as is in the node's attributes. There's little 
> > > magic
> > > here.
> > > 
> > > > Whenever a file does not have the BEOS:TYPE attribute set (for
> > > > whatever
> > > > reason), it could get the type via the file extension only.
> > > 
> > > No, it can't, since you generally can't get the name of a node.
> > Also keep in mind BNode stuff might get used without a valid
> > BApplication/BRoster.
> 
> Our be_roster is initialized at libbe initialization time. All 
> registrar 
> services (MIME types, clipboard, message runners, etc.) are available 
> without a BApplication.

Fair enough :)

> > Now, about FAT: OS/2 and Cygwin use a file named EA DATA.SF to 
> > store
> > extended atributes, probably we could use such a file as well.
> > http://www.win.tue.nl/~aeb/linux/fs/fat/fat-1.html
> 
> If there's a interoperable way to use it, this is certainly a good 
> idea.
> 
I think it's possible.
Some infos:

http://www.tavi.co.uk/os2pages/eadata.html
http://www.warpspeed.com.au/Products/OS2/GU/Manual/appa.htm


> > I think NFSv4 has a form of attribute support as well, didn't dig 
> > in
> > yet, as we only support v2 for now.
> 
> Dito.
http://www.connectathon.org/talks00/shepler.pdf

Now The biggest problem will be mapping those typeless/mindlessly-typed 
attributes to the clean name/type/value model we use.
Why on earth don't everyone use the BeAPI ?

François.