vb .net variables in asp .net

[Matt Mercer]

Hi,

I have a simple question about vb .net variables. There is so much
info on variables out there I had trouble finding exactly what I am
looking for. Here is the question:

When I use a variable (for example Dim strWhatever As String) in
server code, is a new instance of the variable create for each user
who visits the page? I know I need session variables for user specific
information across multiple pages (there are other ways but session is
easiest). But if I'm using variables do something like figure the
interest on a loan payment, and the code is server side (not client
side), will there be a conflict if multiple people use my page
simultaneously or is it all separate? I know this is a rookie question
but I want to confirm the answer. Thanks. If you know of any good
links please send.

[Greg Burns]

It is all separate.

You have to use Session, Application, or Cache to share a variables between
users.

Greg

"Matt Mercer" <ma******@bellsouth.net> wrote in message
news:37**************************@posting.google.c om...

Hi,

I have a simple question about vb .net variables. There is so much
info on variables out there I had trouble finding exactly what I am
looking for. Here is the question:

When I use a variable (for example Dim strWhatever As String) in
server code, is a new instance of the variable create for each user
who visits the page? I know I need session variables for user specific
information across multiple pages (there are other ways but session is
easiest). But if I'm using variables do something like figure the
interest on a loan payment, and the code is server side (not client
side), will there be a conflict if multiple people use my page
simultaneously or is it all separate? I know this is a rookie question
but I want to confirm the answer. Thanks. If you know of any good
links please send.

[Greg Burns]

Uh, well maybe not Session. :^)

"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

It is all separate.

You have to use Session, Application, or Cache to share a variables
between users.

Greg

"Matt Mercer" <ma******@bellsouth.net> wrote in message
news:37**************************@posting.google.c om...

Hi,

I have a simple question about vb .net variables. There is so much
info on variables out there I had trouble finding exactly what I am
looking for. Here is the question:

When I use a variable (for example Dim strWhatever As String) in
server code, is a new instance of the variable create for each user
who visits the page? I know I need session variables for user specific
information across multiple pages (there are other ways but session is
easiest). But if I'm using variables do something like figure the
interest on a loan payment, and the code is server side (not client
side), will there be a conflict if multiple people use my page
simultaneously or is it all separate? I know this is a rookie question
but I want to confirm the answer. Thanks. If you know of any good
links please send.

[Lucas Tam]

ma******@bellsouth.net (Matt Mercer) wrote in
news:37**************************@posting.google.c om:

But if I'm using variables do something like figure the
interest on a loan payment, and the code is server side (not client
side), will there be a conflict if multiple people use my page
simultaneously or is it all separate?

It depends how you declare the variables. If you declare the variable as
static, it will be shared by all the users. If you declare it any other
way, it will be specific for each user.

You can share variables by using static, application, or cache variables.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Bill Borg]

P.S. My understanding is that if you declare a variable static/shared, it's
shared only across that *instance* of the application, and I'm not sure you
can know when/whether IIS decides to fire up a new instance of the app. Can
anybody confirm?

Bill

"Lucas Tam" wrote:

ma******@bellsouth.net (Matt Mercer) wrote in
news:37**************************@posting.google.c om:

But if I'm using variables do something like figure the
interest on a loan payment, and the code is server side (not client
side), will there be a conflict if multiple people use my page
simultaneously or is it all separate?

It depends how you declare the variables. If you declare the variable as
static, it will be shared by all the users. If you declare it any other
way, it will be specific for each user.

You can share variables by using static, application, or cache variables.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[TJS]

it's all separate, each request to the page gets reprocessed for each user.
Their inputs are processed and the variables only represent their
information. So, using something like Dim strWhatever As String is fine.


"Matt Mercer" <ma******@bellsouth.net> wrote in message
news:37**************************@posting.google.c om...

Hi,

I have a simple question about vb .net variables. There is so much
info on variables out there I had trouble finding exactly what I am
looking for. Here is the question:

When I use a variable (for example Dim strWhatever As String) in
server code, is a new instance of the variable create for each user
who visits the page? I know I need session variables for user specific
information across multiple pages (there are other ways but session is
easiest). But if I'm using variables do something like figure the
interest on a loan payment, and the code is server side (not client
side), will there be a conflict if multiple people use my page
simultaneously or is it all separate? I know this is a rookie question
but I want to confirm the answer. Thanks. If you know of any good
links please send.

[Scott M.]

You have to be careful here, "static" means something different in VB.NET
than it does in C#.

If you declare something as "static" in VB.NET, then the variable will
remain in scope even after its' local procedure ends. In VB.NET, if you
declare it as "shared", it is one value that is shared across all instances
of the class within one running application.
"Lucas Tam" <RE********@rogers.com> wrote in message
news:Xn**************************@140.99.99.130...

ma******@bellsouth.net (Matt Mercer) wrote in
news:37**************************@posting.google.c om:

But if I'm using variables do something like figure the
interest on a loan payment, and the code is server side (not client
side), will there be a conflict if multiple people use my page
simultaneously or is it all separate?

It depends how you declare the variables. If you declare the variable as
static, it will be shared by all the users. If you declare it any other
way, it will be specific for each user.

You can share variables by using static, application, or cache variables.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Scott M.]

You won't have conflicts, but you will be creating a new variable for each
user.
"Matt Mercer" <ma******@bellsouth.net> wrote in message
news:37**************************@posting.google.c om...

Hi,

I have a simple question about vb .net variables. There is so much
info on variables out there I had trouble finding exactly what I am
looking for. Here is the question:

When I use a variable (for example Dim strWhatever As String) in
server code, is a new instance of the variable create for each user
who visits the page? I know I need session variables for user specific
information across multiple pages (there are other ways but session is
easiest). But if I'm using variables do something like figure the
interest on a loan payment, and the code is server side (not client
side), will there be a conflict if multiple people use my page
simultaneously or is it all separate? I know this is a rookie question
but I want to confirm the answer. Thanks. If you know of any good
links please send.

[Scott Allen]

A static/shared variable is shared within what's known as an app
domain. If IIS spins up a new instance of an ASP.NET application, it
will live in a new app domain.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 12 Oct 2004 20:05:07 -0700, Bill Borg
<Bi******@discussions.microsoft.com> wrote:

P.S. My understanding is that if you declare a variable static/shared, it's
shared only across that *instance* of the application, and I'm not sure you
can know when/whether IIS decides to fire up a new instance of the app. Can
anybody confirm?

Bill

"Lucas Tam" wrote:

ma******@bellsouth.net (Matt Mercer) wrote in
news:37**************************@posting.google.c om:

> But if I'm using variables do something like figure the
> interest on a loan payment, and the code is server side (not client
> side), will there be a conflict if multiple people use my page
> simultaneously or is it all separate?

It depends how you declare the variables. If you declare the variable as
static, it will be shared by all the users. If you declare it any other
way, it will be specific for each user.

You can share variables by using static, application, or cache variables.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Bill Borg]

Scott, something I've been trying to get an answer to for some time: Can IIS
spin up multiple instances of my application *at the same time*. Or, does it
always end the one before it starts the other? Does it change if I'm working
in a web garden?

Bill

"Scott Allen" wrote:

A static/shared variable is shared within what's known as an app
domain. If IIS spins up a new instance of an ASP.NET application, it
will live in a new app domain.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Tue, 12 Oct 2004 20:05:07 -0700, Bill Borg
<Bi******@discussions.microsoft.com> wrote:

P.S. My understanding is that if you declare a variable static/shared, it's
shared only across that *instance* of the application, and I'm not sure you
can know when/whether IIS decides to fire up a new instance of the app. Can
anybody confirm?

Bill

"Lucas Tam" wrote:

ma******@bellsouth.net (Matt Mercer) wrote in
news:37**************************@posting.google.c om:

> But if I'm using variables do something like figure the
> interest on a loan payment, and the code is server side (not client
> side), will there be a conflict if multiple people use my page
> simultaneously or is it all separate?

It depends how you declare the variables. If you declare the variable as
static, it will be shared by all the users. If you declare it any other
way, it will be specific for each user.

You can share variables by using static, application, or cache variables.

--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/

[Scott Allen]

Hi Bill:

Here is my understanding of the scenario - I think I can find some
official documentation on this if need be.

When a new instance of the application spins up it begins taking
requests before the old instance exists. All new requests are sent to
the new instance of the application while the old instance is allowed
to finish processing any requests it already has in the pipeline
(effectively a drain stop operation, in clustering terms).

I don't think there is any way to have more than one instance of an
ASP.NET application taking on new requests at the same time - except
with web gardening in IIS 6. Then you can have one worker process per
CPU - each taking incoming requests.

Even in a web garden though these are seperate appdomains. Each
instance will have it's own application state and static members.

Actually, I take back what I said in the third paragraph. There
probably are ways to have more than one active instance without
webGardens, but you'd have to write something with ISAPI, so it's
probably not worth the effort, know what I mean?

HTH,

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Wed, 20 Oct 2004 10:07:04 -0700, Bill Borg
<Bi******@discussions.microsoft.com> wrote:

Scott, something I've been trying to get an answer to for some time: Can IIS
spin up multiple instances of my application *at the same time*. Or, does it
always end the one before it starts the other? Does it change if I'm working
in a web garden?

Bill

[Bill Borg]

Scott, this helps, thanks for the additional effort.

"Scott Allen" wrote:

Hi Bill:

Here is my understanding of the scenario - I think I can find some
official documentation on this if need be.

When a new instance of the application spins up it begins taking
requests before the old instance exists. All new requests are sent to
the new instance of the application while the old instance is allowed
to finish processing any requests it already has in the pipeline
(effectively a drain stop operation, in clustering terms).

I don't think there is any way to have more than one instance of an
ASP.NET application taking on new requests at the same time - except
with web gardening in IIS 6. Then you can have one worker process per
CPU - each taking incoming requests.

Even in a web garden though these are seperate appdomains. Each
instance will have it's own application state and static members.

Actually, I take back what I said in the third paragraph. There
probably are ways to have more than one active instance without
webGardens, but you'd have to write something with ISAPI, so it's
probably not worth the effort, know what I mean?

HTH,

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Wed, 20 Oct 2004 10:07:04 -0700, Bill Borg
<Bi******@discussions.microsoft.com> wrote:

Scott, something I've been trying to get an answer to for some time: Can IIS
spin up multiple instances of my application *at the same time*. Or, does it
always end the one before it starts the other? Does it change if I'm working
in a web garden?

Bill