THINK BIG!

quote:

---

My biggest gripe with Snitz is the fact that you don't use Response.write to output pages. Using this already will speed up the board with as much as five times I believe. Another thing that's a pain is the fact that you might start with a table, have a lot of if statements that produces the rest of the table html and sometimes this is really messy to add or take away code. All scripts and data should be seperate from the actual html output. I have just purchased a piece of ASP code for my site that have the whole look and feel of the site incorporated in an simple html file that get's read, so any novice can change the overall look and feel of their site, without having to dable in the asp code, trying to figure out where the table starts, and where the table ends.

---

All the pages are being recoded to response.writes as changes are being made to them for new releases. It's not a minor undertaking, so it will take some time. As for the html file, we've hashed this over and the main problem with this is that using files like that requires the use of the file system object or XML, not all of which is supported by all providers. One of the main goals of Snitz is to keep it as generic as possible to allow as many people to use it as possible.

quote:

---

Another thing I would like to see with Snitz is normalised database for SQL and using stored procedures - this in itself will speed up the board 100% for SQL owners. Now if the code was modular, we could have plugged this in quite easily. I am even prepared to help with this, and if we start some collaboration effort with a couple of dev's, we can have this done in no time.

---

Again, we don't use stored procedures because that would eliminate Access and MySQL users, two databases we currently support.

The modular approach is a valid one, but not on the top of our list unforunately....maybe as we go..

Dave Maxwell
--------------
Proud to be a "World Class" Knucklehead

quote:

---

My biggest gripe with Snitz is the fact that you don't use Response.write to output pages. Using this already will speed up the board with as much as five times I believe.

---

quote:

---

quote:

---

My biggest gripe with Snitz is the fact that you don't use Response.write to output pages. Using this already will speed up the board with as much as five times I believe. Another thing that's a pain is the fact that you might start with a table, have a lot of if statements that produces the rest of the table html and sometimes this is really messy to add or take away code. All scripts and data should be seperate from the actual html output. I have just purchased a piece of ASP code for my site that have the whole look and feel of the site incorporated in an simple html file that get's read, so any novice can change the overall look and feel of their site, without having to dable in the asp code, trying to figure out where the table starts, and where the table ends.

---

As for the html file, we've hashed this over and the main problem with this is that using files like that requires the use of the file system object or XML, not all of which is supported by all providers. One of the main goals of Snitz is to keep it as generic as possible to allow as many people to use it as possible.

---

Yes and no? I guess it depends on what we're talking about.

It could be that you have a sub for the navigation and other forum elements. You could wrap the html into subs too. If in the one html sub you want the navigation to appear, you call the nav sub.

Before someone says that inc_top.asp and inc_footer.asp do something similiar, I agree to a point, but it's not too easy to follow, 'specially for first-timers.

The Writer Community

"Do not go where the path may lead, go instead where there is no path and leave a trail."
-Ralph Waldo Emerson

• Speed up database queries


• Accellerate your ASP script


• Tune IIS


• Bypass the ODBC layer


• Choose the appropriate recordset options


• Close connections as soon as possible


• Use stored procedures


• Use disconnected recordsets


• Enable Connectin pooling



To further elaborate on Accelerate Your ASP script, here are the things you MUST do:

• Use local variables whenever possible


• Batch Response.Write statements


• Avoid resizing dynamic arrays


• Turn on Option Explicit


• Copy collection values to local variables


• Don not store OBJECTS in the Session object


• Avoid running a site as an isolated process


• Use the cache of the browser


• Buffer output


• Use compiled objects


• Do performance testing


As you can see, we violate a couple on Snitz code. I will be happy to tell you where you can get further information on each of these bullets, just e-mail me. But let me conclude with why you should batch Response.Write statements.

I agree five times is not likely to happen, maybe at least double as fast, in the current scenario, the script jumps from ASP code to HTML and back in every line. This is particulary of note with line where a variable is written like <% =DBNTusername %>. If the code was a batched Response.write statement, it would not have to do this, ie. jump between ASP and HTML. Think about tables where topics or outputted. Right now it has to do a lot of jumping. I use some applications that is completely written in batched Response.write statements, and those applications also do a lot of table operations, and they do perform better on average compared to Snitz.

Since we already have a variable for database handler, it would be cool if we can convert SQL code to stored procedure, since this execute on the server, and does give much better response.

Sorry for the longwinded explanation, but you asked.

Thanks
Eddie