Asp and Application.lock

[Jennifer.Berube]

What is it exactly that makes application.lock such a bad thing? I
just need a better explanation or link to a resource desribing it's
downfall.

[Eliyahu Goldin]

As everything else, it is bad if misused. It is good for ensuring data
integrity on short operations. But it locks the application and forces other
requests to queue up. A sort of bottleneck.

--
Eliyahu Goldin,
Software Developer & Consultant
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net
<Je*************@gmail.comwrote in message
news:11**********************@w1g2000hsg.googlegro ups.com...

What is it exactly that makes application.lock such a bad thing? I
just need a better explanation or link to a resource desribing it's
downfall.

[Juan T. Llibre]

Access to the Application object is serialized to prevent the corruption
which could occur if more than one user writes to it at the same time.

The requests to modify application variables are queued up,
and they are given access in the order they were received.

That reduces performance somewhat, but prevents data corruption.

You should try to avoid letting users change application variables.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<Je*************@gmail.comwrote in message
news:11**********************@w1g2000hsg.googlegro ups.com...

What is it exactly that makes application.lock such a bad thing? I
just need a better explanation or link to a resource desribing it's
downfall.

[Jennifer.Berube]

On Apr 10, 11:27 am, "Juan T. Llibre" <[e-mail]>
wrote:

Access to the Application object is serialized to prevent the corruption
which could occur if more than one user writes to it at the same time.

The requests to modify application variables are queued up,
and they are given access in the order they were received.

That reduces performance somewhat, but prevents data corruption.

You should try to avoid letting users change application variables.

Juan T. Llibre, asp.net MVP
asp.net faq :http://asp.net.do/faq/
foros de asp.net, en español :http://asp.net.do/foros/
===================================<Jennifer.Ber.. [e-mail] in message

news:11**********************@w1g2000hsg.googlegro ups.com...

What is it exactly that makes application.lock such a bad thing? I
just need a better explanation or link to a resource desribing it's
downfall.- Hide quoted text -

- Show quoted text -

Well see....we had a huge bottleneck where the server rose up to 94%
usage and it was due to an application.lock command in a global.asa
file. It is for a visitor counter...

[Juan T. Llibre]

re:

It is for a visitor counter...

One of the flimsiest reasons to use Application.Lock.

I'd prefer to write to a text file which, even though it's also serialized,
creates far less contention than going through Application.Lock/Unlock.

There's a fairly decent sample you could adapt here :
http://www.asp101.com/samples/counter_aspx.asp

And there's another sample here :
http://www.codeproject.com/aspnet/EasyHit.asp

Adapt either one. Either that, or use a commercial counter.
Use *anything*, except code that uses Application.Lock/Unlock.

;-)


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
<Je*************@gmail.comwrote in message
news:11*********************@q75g2000hsh.googlegro ups.com...
On Apr 10, 11:27 am, "Juan T. Llibre" <[e-mail]>
wrote:

Access to the Application object is serialized to prevent the corruption
which could occur if more than one user writes to it at the same time.

The requests to modify application variables are queued up,
and they are given access in the order they were received.

That reduces performance somewhat, but prevents data corruption.

You should try to avoid letting users change application variables.

Juan T. Llibre, asp.net MVP
asp.net faq :http://asp.net.do/faq/
foros de asp.net, en español :http://asp.net.do/foros/
===================================<Jennifer.Ber.. [e-mail] in message

news:11**********************@w1g2000hsg.googlegro ups.com...

What is it exactly that makes application.lock such a bad thing? I
just need a better explanation or link to a resource desribing it's
downfall.

Well see....we had a huge bottleneck where the server rose up to 94%
usage and it was due to an application.lock command in a global.asa
file. It is for a visitor counter...

[Jennifer.Berube]

On Apr 10, 2:16 pm, "Juan T. Llibre" <[e-mail]>
wrote:

re:

It is for a visitor counter...

One of the flimsiest reasons to use Application.Lock.

I'd prefer to write to a text file which, even though it's also serialized,
creates far less contention than going through Application.Lock/Unlock.

There's a fairly decent sample you could adapt here :http://www.asp101.com/samples/counter_aspx.asp

And there's another sample here :http://www.codeproject.com/aspnet/EasyHit.asp

Adapt either one. Either that, or use a commercial counter.
Use *anything*, except code that uses Application.Lock/Unlock.

;-)

Juan T. Llibre, asp.net MVP
asp.net faq :http://asp.net.do/faq/
foros de asp.net, en español :http://asp.net.do/foros/
===================================<Jennifer.Ber.. [e-mail] in message

news:11*********************@q75g2000hsh.googlegro ups.com...
On Apr 10, 11:27 am, "Juan T. Llibre" <[e-mail]>
wrote:

Access to the Application object is serialized to prevent the corruption
which could occur if more than one user writes to it at the same time.

The requests to modify application variables are queued up,
and they are given access in the order they were received.

That reduces performance somewhat, but prevents data corruption.

You should try to avoid letting users change application variables.

Juan T. Llibre, asp.net MVP
asp.net faq :http://asp.net.do/faq/
foros de asp.net, en español :http://asp.net.do/foros/
===================================<Jennifer.Ber.. [e-mail] in message

news:11**********************@w1g2000hsg.googlegro ups.com...

What is it exactly that makes application.lock such a bad thing? I
just need a better explanation or link to a resource desribing it's
downfall.

Well see....we had a huge bottleneck where the server rose up to 94%
usage and it was due to an application.lock command in a global.asa
file. It is for a visitor counter...- Hide quoted text -

- Show quoted text -

I agree...I'm the administrator but because I used to be a developer I
have become quite useful to the company because I can point out errors
in the coding. I just needed a solid answer to application.lock. I
was always taught it was a "no no" and to never do so I never really
looked into it further. Thanks!