One or multiple command objects for ASP.NET app to MSSQL (or Acces

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

In my web application I am using one single command object to do stuff with
the db (UPDATE, INSERT etc). for all user sessions. Does it make any
difference if I:

a. Keep it this way
b. create new command for each routine
c. create new command for each session.

Any comments are greatly appreciated.

Thank you
 
Alex,

When you do not use a class shared, however instance it everytime, it is
always an independend object in your page at serverside for that session
which lives as long as the page is processed at the server.

Cor
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Multiple threads or app instances? 2
entity framework patten for asp.net; need get it back again to update? Keep objectContext in Applica 1
Potential bug: ASP.NET session variables and file watcher service 1
What's better: using Application or Session object?? (in my case) 2
What's the best way to mirror asp.net session variables acrossservers? 1
Need some help for sending custom commands from ASP.NET page 1
accessing another user's session state 6
How to loop till the last or null row. 2

Back
Top