know where >> it is, exactly, so I have to try a bunch of different
options. If all of >> the options along the way are a bit slow (let's
say 2-5 seconds each), my >> brain starts to smoke and I go elsewhere
if possible. >>
>>
>> 2) I browse around a site with quick loading pages, and then get to
the tool >> that is clearly what I want. Let's say it searches some
database for hat >> sizes of celebrities. Perfect! I want to know
what size hat to buy John >> Cleese for his birthday. I enter John in
the first name field, Cleese in >> the last name field, and wait 43
seconds for the query to load. My brain >> does not start to smoke.
The theory in that is a very very good answer... finally a pretty
balanced point... altho you may want to cache that 43 second query
somehow so that it isn't that long the next time round :)
I'll agree with that though...
--
dc
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
