SyncLock Question

[JumpsInLava]

I have an asp.net module that does stuff kind of like this:

 

 

Module Stuff

   Dim strHold As String = String.Empty

   Public Sub subDoStuff(ByVal strString As String)
       'Added SyncLock do to paranoia
       SyncLock GetType(Stuff)
           'Clears strHold
           strHold = String.Empty
           'Calls subProcess that does some stuff with strHold
           subProcess()
           'Does some more stuff with strHold
           strHold &= strString
           'Writes strHold somewhere
       End SyncLock
   End Sub

   Private Sub subProcess()
       'Adds some stuff to strHold
       strHold = "This and that"
   End Sub

End Module

 

 

I saw some samples that used SyncLock, got paranoid, and added it to all of my modules that use any type of globals. (I know global variables are the root of all evil, and will cause nations to collapse, but they sure are handy some times.)

 

Question 1: Do I need to use SyncLock?

Question 2: If so, should I use "SyncLock GetType(strHold)" instead?

[JumpsInLava]

May be an better question would be:

 

In ASP.NET, is each client session its own "application" on the server, or is each client session multi-threading from the same code on the server?

[Robby]

Yes "each client session its own "application" on the server"

[JumpsInLava]

Hmmmmm. Interesting.

 

Thank you for the response.