From: Nick Roberts <nick.roberts@acm.org>
Subject: Re: Latin_1 and portability
Date: Sun, 14 Dec 2003 06:12:55 +0000
Date: 2003-12-14T06:12:55+00:00 [thread overview]
Message-ID: <brgv18$31u4n$1@ID-25716.news.uni-berlin.de> (raw)
In-Reply-To: <gbSCb.107593$_M.565680@attbi_s54>
Jeff C, wrote:
> "Bj�rn Persson" <bjorn_persson.spam-is-evil@sverige.nu> wrote in message
> news:20031214034629.3960d5a8.bjorn_persson.spam-is-evil@sverige.nu...
> > As a result, the file server can't know which files should be converted, it
> > can't know which format to expect from a certain client, and it can't know
> > which format a certain client needs; and there's not much AdaOS can do to
> > help.
>
> Ah..But you miss the ultimate power of AdaOS. Since it does not exist and is
> never likely to exist, it is capable of claiming to perform all sorts of
> endless wonders...
It's true that AdaOS does not yet exist, and it surely will not for several
years yet, but I remain as determined as ever to see it through, however
long that takes.
Anyway, it's not really of importance to Bj�rn's point. I think all he
meant to imply is that there's not much /some future operating system/ can
do to help. In essence, that's quite correct. However, for the curious,
AdaOS will have a way of coping with the problem (as it will have to, of
course).
AdaOS will be object oriented, and files will be objects, and so strictly
typed. Of course one type will be 'opaque binary', but all text files will
have suitable types, parametised by encoding and character set.
I anticipate developing (and evolving) a piece of software in AdaOS which
will use a strategy to guess the correct type of imported files. When
obtaining a file by HTTP or FTP, it may be able to obtain a MIME type
string, for example. For files coming from some kinds of systems, it may
use a part of the name (the 'file type extension'). It may examine the
file's contents. It might ask the user to supply or confirm the type.
(Generally, the user will have to be asked for other information about the
file anyway.)
Normally, every external file imported into a system will be permanently
represented by an internal object. In this object will be stored a lot of
information about the external file, including the (confirmed) type, and
this type would generally be re-used whenever the file was re-accessed. (In
fact, the file contents may be temporarily cached in the object anyway,
according to parametised criteria.)
--
Nick Roberts
__________________________________________________________
| Fight Spam! Join EuroCAUCE: http://www.euro.cauce.org/ |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2003-12-14 6:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 15:24 Latin_1 and portability amado.alves
2003-12-14 2:46 ` Björn Persson
2003-12-14 5:04 ` Jeff C,
2003-12-14 6:12 ` Nick Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-13 13:35 amado.alves
2003-12-13 14:54 ` Björn Persson
2003-12-13 22:17 ` Larry Kilgallen
2003-12-14 1:55 ` Björn Persson
2003-12-13 22:21 ` Larry Kilgallen
2003-12-13 2:27 amado.alves
2003-12-13 13:09 ` Larry Kilgallen
2003-12-10 13:16 amado.alves
2003-12-10 12:15 Xavier Serrand
2003-12-10 13:45 ` Georg Bauhaus
2003-12-10 22:00 ` Xavier Serrand
2003-12-10 18:33 ` Jeffrey Carter
2003-12-10 21:34 ` Pascal Obry
2003-12-10 21:52 ` Ludovic Brenta
2003-12-11 3:40 ` Robert I. Eachus
2003-12-12 23:41 ` Larry Kilgallen
2003-12-13 14:48 ` Robert I. Eachus
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox