Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Major mixup in two ASP.NET transactions
Message
De
03/09/2006 18:44:08
 
 
À
03/09/2006 18:16:23
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Versions des environnements
Environment:
VB 8.0
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
01150471
Message ID:
01150635
Vues:
45
Hi,

>Those are properties that are reset everytime a hit is done. This is in BeginRequest().
>
>
>            cCookie = ""
>            cDecrypt = ""
>            cEncrypt = ""
>            cError = ""
>            cIP = oRequest.ServerVariables("REMOTE_ADDR")
>            cQueryString = oRequest.QueryString.ToString()
>            cPage = ""
>            cPassword = ""
>            cSession = ""
>            cSession2 = ""
>            cUrlReceived = GetUrlReceived()
>            cUrlReceivedOriginal = cUrlReceived
>            cUsername = ""
>            lCookie = False
>            lError = False
>            lRemember = False
>            nDateNow = Date.Now.Ticks
>            nLanguage = 1
>            nNoMember = 0
>            oBrowser = oRequest.Browser
>            oCookie.Clear()
>            oJavascriptInclude.Clear()
>            oJavascriptMessage.Clear()
>
>
>Those properties are related and dependant on every hit. So, I need to isolate that from the start to the end of the process. If I can initialize a copy of the framework at startup, I would be ok. Because, if another hit is changing nLanguage, for example, I would be sure this would have been changed in that hit framework copy object and not in this one.

No simple fix for these. Maybe you should store the items that aren't Request/Response related in the Context.Items collection rather than as framework properties. It would mean fairly substantial changes to your existing code but I see no obvious alternative.

Regards,
Viv
(P.S. Sloping off soon so ....)
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform