Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Handling first hit on a site
Message
De
27/09/2010 18:00:34
 
 
À
27/09/2010 17:37:40
Mike Cole
Yellow Lab Technologies
Stanley, Iowa, États-Unis
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Versions des environnements
Environment:
VB 9.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01482914
Message ID:
01482953
Vues:
43
I have moved the LockObject declaration in my oApp class, which is Shared. This seems to be much better. Basically, the following attached file demonstrates this logic.

By looking at it, you will see that a lot of hits happened in the same second when I sent a new DLL. However, only one hit (represented here by the file name - ordered in sequence), got into the initialization process. All other hits fall into a pending mode and jumped directly to the end once the lock was released, thus oApp.lInitializeWeb was then set to True.
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform