The need for IE-only sites? (was RE: [thelist] Identify a Web Crawler's request)

David Travis dwork at
Wed Jul 7 12:55:09 CDT 2004

Hi Chris,

Me again... Xmls are only an example... I guess I failed to reflect it in my
post. Add to it also user experience using proprietary DHTML, styles, and

Remember that only since N6 Mozilla browsers actually started supporting
cool stuff, which were supported LONG time before in IE. That's a fact I had
to cope with when the project started.

Again, the Hebrew issue... when you develop a site that has to look good you
cannot compromise on "ugly fonts" as someone stated in one of the posts
regarding Netscape's Hebrew rendering...


-----Original Message-----
From: thelist-bounces at
[mailto:thelist-bounces at] On Behalf Of
chris at
Sent: Wednesday, July 07, 2004 4:22 PM
To: thelist at
Subject: Re: The need for IE-only sites? (was RE: [thelist] Identify a Web
Crawler's request)

> I find this somewhat naive. You are finding fault in him approximating
> a network architecture that is more appropriate for the application?

In a commercial environment one should build an infrastructure and
incorporate an architecture that most effectively support the application.

> Would you find the same fault in someone who has decided to use a
> dual-processor server instead of a server with one "really beefy"
> processor (you might consider the analogy invalid, but parallel
> processing is very similar to what we're talking about here)?

That would depend. The original post made reference to manipulating XML
using XSLT on the client rather than the server in order to lower the load
on the server. I would be interested to know why and how the conclusion was
drawn that the server would not be able to cope with the load.

> I would suspect not.

I wouldn't know what exactly a "really beefy" processor would be in real
terms; but the decision to use parallel processors versus a single, higher
specification processor would depend on the application being run on the
box. Without further qualification it would be impossible to comment.

> In fact, there are many applications on the Web which have
> more-than-normal processing on the client in the forms of java
> applets, activex controls, and even javascript.

The reason these technologies are used is [usually] not to reduce the load
on the server, thus their mention is irrelevant to the discussion at hand.


Chris Marsh
* * Please support the community that supports you.  * *

For unsubscribe and other options, including the Tip Harvester 
and archives of thelist go to: 
Workers of the Web, evolt ! 

More information about the thelist mailing list