#
Greetings, Lynx users. There is a reason this page doesn't use ALT tags
on the images. The reason is that the bozos responsible for both MSIE
and Netscape Confusicator 4.0 decided that they would display the ALT
tags of images every time you move the mouse over them -- even if the
images are loaded, and even if they are not links. The ALT attribute
to the IMG tag is supposed to be used *instead of* the image, not *in
addition to* the image.
This looks absolutely terrible, so I don't use ALT tags any more in
self-defense.
If they wanted to implemented tooltips, they should have used the TITLE
attribute to the A tag. That's in the HTML 1.2 spec and everything.
I had to decide between making this page look good for the vast majority
of viewers, or making it be readable by the miniscule minority of you
stuck in the 70s. Those of you in the retro contingent lost. Sorry.
#
Given that we are able to get ~50k entries / second with a tethereal output parsed via lex/yacc -> postgresql on a moderate pc I would more amazed at what level of analysis they are providing. Also the data does tend to have some importance over time for those transient issues. Add a hash to your parser and you can just aggregate the data to reduce the load on the db.
Slashdot Mirror
http://www.linbsd.org/logo/freebsd_small.png
Lynx users might remember this from www.jwz.org
/ /w ww.jwz.org/
#
Greetings, Lynx users. There is a reason this page doesn't use ALT tags
on the images. The reason is that the bozos responsible for both MSIE
and Netscape Confusicator 4.0 decided that they would display the ALT
tags of images every time you move the mouse over them -- even if the
images are loaded, and even if they are not links. The ALT attribute
to the IMG tag is supposed to be used *instead of* the image, not *in
addition to* the image.
This looks absolutely terrible, so I don't use ALT tags any more in
self-defense.
If they wanted to implemented tooltips, they should have used the TITLE
attribute to the A tag. That's in the HTML 1.2 spec and everything.
I had to decide between making this page look good for the vast majority
of viewers, or making it be readable by the miniscule minority of you
stuck in the 70s. Those of you in the retro contingent lost. Sorry.
#
reference:
http://web.archive.org/web/20000303115840/http:
For those lynx users among us maybe you remember seeing this if you ever visited jwz.org
w ww.jwz.org/
reference http://web.archive.org/web/20000303115840/http://
Given that we are able to get ~50k entries / second with a tethereal output parsed via lex/yacc -> postgresql on a moderate pc I would more amazed at what level of analysis they are providing. Also the data does tend to have some importance over time for those transient issues. Add a hash to your parser and you can just aggregate the data to reduce the load on the db.
Given what a good filesystem DFS is this will be nice to have access to all the features of DCE/DFS and give OpenAFS a run for its money.
But seriously DFS has a lot of core features that can even cause problems for DFS vendor Entegrity.
I smell a new project called OpenDFS