stormin61931
Member
Excellent, Phil! All is working fine on IE 5.5 and IE 6.0.
-stormin
-stormin
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yes, one might say that this format supports breaking off from the thread into "very specific and individual discussions" which take away from the value of the original thread and leads to long, useless and pointless threads, but I guess that is a point of view thing.Sorry, but that isn't going to change. Our system supports
multiple sub-threading, something UBB can't do, this means that
many of our threads grow into very specific and individual
discussions 'beneath' the original posting.
200K? Actually UBBS pages, so you get something much smaller, perhaps 50k, so you can see what the tread is about and you don't have to click fifty times to find out the thread didn't have a single intresting thing in it, but again my point of view.Clicking to read a
message and getting a 200 - 300 KB page of messages back isn't (a)
clever, (b) useful or (c) a good way to reduce bandwidth usage.
Yes, your point of view.These forums are the most popular and heavily used of any site I
know, the reason is BECAUSE of the way they operate. I'm not going
to break that, the majority of users prefer this format.
Sorry, but that isn't going to change. Our system supports
multiple sub-threading, something UBB can't do, this means that
many of our threads grow into very specific and individual
discussions 'beneath' the original posting. Clicking to read a
message and getting a 200 - 300 KB page of messages back isn't (a)
clever, (b) useful or (c) a good way to reduce bandwidth usage.
These forums are the most popular and heavily used of any site I
know, the reason is BECAUSE of the way they operate. I'm not going
to break that, the majority of users prefer this format.
Hi guys,
After a few sluggish days last week I started work on a higher
performance forums application. It looks and feels EXACTLY the
same as the current pages but works in a very different way. Our
current forums are crippled by the fact that every message read
(read.asp) accesses the database (500,000 times a day), this puts
load on our database and web servers. The new system is simple
enough, make read.asp cacheable (ie. if you've read the message
before your browser won't ask for it again) but make the thread
list dynamic (as that can change by the minute). This new system
should be (a) faster for you as a user of the forums, (b) put less
stress on our servers and (c) help to reduce our huge bandwidth
usage.
If you feel like you'd like to help beta test the new pages they
can be found here:
http://www.dpreview.com/forums2/
Remember, it (should) look and feel almost identical to the
existing system but reading messages (especially multiple messages
in the same thread) SHOULD feel faster.
Caveats:
The new pages will work ONLY with Javascript enabled browsers
(IE4+, NS4+, Opera 5+) - this is non-negotiable.
There may be a few 'gotchas', make notes in this thread if you have
found a serious issue.
While in the "my Threads" page, if I click on "NEW" on one of my
threads, I get:
"An Error of the type "Microsoft VBScript runtime " has occurred"
From the old forums page, this works ok.
TS
at least for the client end.
You may see some stats that indicate it is better but really, the
only problems I had was when the activity was very high. Doubt that
it is now.
However I will say that it "feels' better and theoretically if we
can reduce the calls to the DB it should remain so in periods of
high activity.
Homer
Yes, seems faster under IE5.5 with dial-up at 44k. Clicking on
poster's "profile" under the beta yields:
"Forbidden
"This page is protected by proprietary privacy software (to protect
users email addresses).
"Your web browser did not pass the correct credentials to our server
"You may receive this message if you are blocking certain HTTP
headers"
whereas the profile comes up fine under the Mark I model. Not
plugged in, or is this a permanent de-feature?
-jrad
I just went from top to bottom of this thread:
http://www.dpreview.com/forums/read.asp?forum=1018&page=1&message=1753908
by cont. pressing next on the header. And then the same thread in
http://www.dpreview.com/forums2/read.asp?forum=1018&page=1&message=1753908
The new Higher Perf Forums took 8 minutes. The old one clocked in
with 1 minute - ehhh - Higher Perf??
Magne
Using IE 5.0 SP2 on W2K.
Yes - I'm sure the second round was on the old forums - no caching
showed up on the item - they were all new and unread...
Hi guys,
After a few sluggish days last week I started work on a higher
performance forums application. It looks and feels EXACTLY the
same as the current pages but works in a very different way. Our
current forums are crippled by the fact that every message read
(read.asp) accesses the database (500,000 times a day), this puts
load on our database and web servers. The new system is simple
enough, make read.asp cacheable (ie. if you've read the message
before your browser won't ask for it again) but make the thread
list dynamic (as that can change by the minute). This new system
should be (a) faster for you as a user of the forums, (b) put less
stress on our servers and (c) help to reduce our huge bandwidth
usage.
If you feel like you'd like to help beta test the new pages they
can be found here:
http://www.dpreview.com/forums2/
Remember, it (should) look and feel almost identical to the
existing system but reading messages (especially multiple messages
in the same thread) SHOULD feel faster.
Caveats:
The new pages will work ONLY with Javascript enabled browsers
(IE4+, NS4+, Opera 5+) - this is non-negotiable.
There may be a few 'gotchas', make notes in this thread if you have
found a serious issue.
Hi guys,
After a few sluggish days last week I started work on a higher
performance forums application. It looks and feels EXACTLY the
same as the current pages but works in a very different way. Our
current forums are crippled by the fact that every message read
(read.asp) accesses the database (500,000 times a day), this puts
load on our database and web servers. The new system is simple
enough, make read.asp cacheable (ie. if you've read the message
before your browser won't ask for it again) but make the thread
list dynamic (as that can change by the minute). This new system
should be (a) faster for you as a user of the forums, (b) put less
stress on our servers and (c) help to reduce our huge bandwidth
usage.
If you feel like you'd like to help beta test the new pages they
can be found here:
http://www.dpreview.com/forums2/
Remember, it (should) look and feel almost identical to the
existing system but reading messages (especially multiple messages
in the same thread) SHOULD feel faster.
Caveats:
The new pages will work ONLY with Javascript enabled browsers
(IE4+, NS4+, Opera 5+) - this is non-negotiable.
There may be a few 'gotchas', make notes in this thread if you have
found a serious issue.
Hi guys,
After a few sluggish days last week I started work on a higher
performance forums application. It looks and feels EXACTLY the
same as the current pages but works in a very different way. Our
current forums are crippled by the fact that every message read
(read.asp) accesses the database (500,000 times a day), this puts
load on our database and web servers. The new system is simple
enough, make read.asp cacheable (ie. if you've read the message
before your browser won't ask for it again) but make the thread
list dynamic (as that can change by the minute). This new system
should be (a) faster for you as a user of the forums, (b) put less
stress on our servers and (c) help to reduce our huge bandwidth
usage.
If you feel like you'd like to help beta test the new pages they
can be found here:
http://www.dpreview.com/forums2/
Remember, it (should) look and feel almost identical to the
existing system but reading messages (especially multiple messages
in the same thread) SHOULD feel faster.
Caveats:
The new pages will work ONLY with Javascript enabled browsers
(IE4+, NS4+, Opera 5+) - this is non-negotiable.
There may be a few 'gotchas', make notes in this thread if you have
found a serious issue.