About the Chipdir
Well, because it's useful to use. Mainly for you the viewer. This site
is being mirrored to about 30 sites all over the world because of the
international internet bandwidth limitations that existed from the start
of the WWW. (The required backbone capacity of the Net doubles every
three months and the phone companies are already handling more data
over their lines than speech for several years now. The required
speech capacity doesn't grow exponentially, so it was unavoidable...)
Well, because the Chipdir is being mirrored to all kinds of systems
and because most of the people managing these sites have busy jobs
it's impossible to install search engines on all these sites and
because of the bandwidth problem the search engine can also not be
located on a central site. (And it would also ruin the concept that
the Chipdir is completely CD-ROM'able...).
kind of off-line search engine.
When Java became popular they renamed it hoping to gain from Java's
doesn't load slowly: It loads together with your normal HTML page and
just don't execute it. JS scripts are usually quite small and don't need
to load big libraries with subroutines.
and can hardly do anything with your harddisk or printer or whatever
because it was designed to be very safe for the websurfer so there was
no trust issue as regards to surfing to unknown sites.
computers with small memories.
Jörg Wunsch disagrees:
Cookies (see elsewhere) have also been designed to be as privacy friendly
as possible. They were mainly meant to enable shopping basket applications,
so you could order a couple of things on a WWW shop site and then remove them
again and pay for them all at once at the end if you so choosed to.
leaves in a special file on your computer (in netscape/cookie.txt or something
like that) so it can recognize you between the pages that you request. The
HTML protocol is purely page by page based and doesn't offer a sure way
to recognise people between pages. Besides being able to tag people using
a cookie and keeping the data in it's own centralized database it can also
ask the browser to store the data on the users computer, which is even
less privacy sensitive I think... You're free to erase the complete cookie
file whenever you like or even erase it line by line if you so choose.
A cookie can only be asked back by the site that placed it, by the way, so
it's not a way via which sites can share information. This also makes it less
useful for the Chipdir with it's many mirror sites unfortunately. :-(
The CGI-scripts of the previous generation could also write and read
cookies and could even communicate them with the central database which
No not yet. Why not? It hasn't been worth the effort yet...
[199906: Not true anymore, I introduced them in the 9905 version and haven't had
a single complaint... Jaap]
From: Jaap van Ganswijk <email@example.com>
Subject: Re: [js-talk] How Learn JS?
At 18:18 1997-07-25 -0400, Arthur Dardia wrote:
>book? If so, what book? I barely know anything, but I figured I could
>learn from this mailing list. Please help me.
You can also use the on-line JS documentation from NetScape:
The book is clearly based on this NetScape data, but I prefer to learn
from a book and later have it as a reference next to my computer.
- Too big characters fonts
- Too many examples
(Which eliminates the books of most other publishers.)
I think the O'Reilly books are generally very serious and good
and plan to buy O'Reilly books only in future (whenever possible).
site and you can also buy a set of five WWW books on a CD-ROM,
but I really would prefer to have the real books...
(No I'm not associated with O'Reilly...;-)