Need Information on ASP.NET Application Thead Safety

Greetings,

I will be building an ASP.NET application to process orders in a multi-user environment, and I am thinking about thread safety considerations with the class model and usage in my design.   This application will access a DB2 database on an IBM iSeries platform on the back-end, using the IBM DB2 data provider for .NET.  

In a nutshell, the page (UI) classes will create local instances of business-layer classes (order, customer, etc.), which in turn, will contain references to data-layer classes that utilize the IBM .NET data provider to read and write data.  So, the overall design of the program flow will be:
 
Web UI (page classes) --Ref--> Business Classes (DLL) --Ref--> Custom Data Layer (DLL) --Ref--> IBM .NET Data Provider --accesses-->) DB2 database (IBM i Series)
 
With this design model, I need to know what considerations should be addressed regarding thread safety, to avoid problems in a multi-user environment.  I have only a few shared public functions in a global module, but these do not affect data in any way.  They are used to perform fixed calculations or return static information from fixed lists, config file settings, etc.  
 
In my page code-behind, I'll be creating class instances that will handle the actual work and business logic.  These will be private to the page, and destroyed at the completion of the page life cycle.  Example:  The EnterOrder class (EnterOrder.aspx) references three business objects…
 
Public Class EnterOrder
    Inherits ProtectedOEWebPage   <--- (custom class; inherits from System.Web.UI.Page)
 
    Protected cobjOrder As Order    <---- (classes in referenced business object DLL)
    Protected cobjCustomer As Customer
    Protected cobjItem As Item

 
Then, in the Page_Load event, to load data for an existing order:
 
    cobjOrder = New Order()
    cobjOrder.Load(OrderID)   <-- Passed in query string for existing order
 
In the Order.Load event:

   iDB2Connection connection = new iDB2Connection(ConnectionString);   <-- from web.config
   iDB2Cmd = new iDB2Command("CALL oeGetOrder( ? )", connection);  <-- OrderID passed as input, stored procedure on IBM i Series
   iDB2DataReader driDB2Reader = iDB2Cmd.ExecuteReader();

  ... <process data reader and return record to calling function> ...


Do I need to be concerned with thread safety using this model, when multiple users are accessing the application, since business object variables are declared as protected within the page class?  Would IIS not create a separate, protected instance of each page class and referenced objects for each user session?  This application will, for the most part, be using Ajax posts to update and retrieve data, instead of page post backs. For example, user types a customer ID, and tabs out of that field.  An Ajax post is triggered, the customer ID is validated with a database call, and if valid, the ID is updated in the order table and the customer name is also refreshed on the page.  I need to ensure that this kind of end-to-end process is thread safe and without potential for conflict between users.

To summarize:

1.  Is this design thread-safe?
2.  As IIS handles multiple instances of the application and requests to read/update data from the users, will it segregate/protect instances of objects that are created for each session?
3.  If static shared functions or methods are used, should they be used sparingly, and if so, in what situations are they considered acceptable?
 
Thank you in advance.
bm5034Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

apeterCommented:
1. It is thread safe. You are following common practice 3tier model.
2. For each user request, there will be a separate thread to process so the object instances are safe across users.
3.static methods are thread safe by default.

Just thought will reiterate which you might have already doing.

Dispose your connection objects or any resources consumed throught the project.
Cache static values in the sever to minimise the database hits.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Applications

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.