>Well, I just need to make sure of a specific information here. It is true that everything runs much faster. And, that makes it that people are use to get whatever they want in instant access. And, for some, if one specific transaction takes one additional second, it would then be the end of the world. I mean, are those reports coming from other members related to a timeout of 10 to 20 seconds or just that extra second. lol

You have to understand the programmers being frustrated by their users every day and on a daily basis, and then once they get their chance to vent, when they can play users themselves. I guess some would vent some extra pressure :).

Generally, most of it is instantaneous, with a two exceptions at times - more below.

>If this is in regards to posting a message, well, that one is a heavy transaction and could take a second or two. But, in general, the response time is under 0.2 second. That is the respond time of the server. So, the transfer is something we do not control and might go up to a second or two at the other end until the transaction is full received.

I have got a "try again" from FF3 twice today after posting a message. The trouble was that I didn't know what will it try again - to post the message, or to display it when it's posted. Experience with various web servers tells me there's maybe 2:1 chance the latter is the case, i.e. the message was posted OK, but it takes some time to get it updated, retrieved, rendered, HTTP'd to my browser. Luckily, I knew a way to see which of these happened (looked up the previous message in a new tab, then there view subsequent messages) and it was the former, so I gave it a "try again" and then it went fine. And fast, too.

>I haven't sent a new compile since a while. But, when I do, it takes 12 seconds approximately under IIS refreshes it into .NET.

The only other time when it's visibly slow is when displaying the table with replies to my messages. There's almost regularly a second or two between displaying the header of that table and its rows (even if it's the blank row with "no new messages"). Which isn't a show stopper of any kind - just reporting on how it looks from here.