Singleton design approach 
Author Message
 Singleton design approach

We are not sure whether we am getting this right regards
the Singleton Object.

Intially we thought it would be a good idea to have our
Business & DAL objects
as Singleton Objects  with static methods so that there
isnt an overhead to instantiating them.
But decided against that pattern after hearing that all
such static methods will just have a single thread of
execution is this true and wouldnt service more than one
client at any given time.

What are the pros and cons of using such a design

Will there be any scalability issues since there is just
one instance maintained in a Singleton approach.

Well the Application blocks helper classes from Microsoft
seem to follow this approach.

we are worried whether such objects will be able service
multiple client requests simultaneously

Any sample illustrations would be higly regarded

Mon, 28 Mar 2005 13:57:40 GMT  
 [ 1 post ] 

 Relevant Pages 

1. Good design approach?

2. Using the system tray icon (design/impl approach)

3. Newbie: Help regarding design approach

4. Looking for opinions on design approach -- using database with multiple views

5. Singleton Design Pattern Question

6. Proper Singleton Design in C#

7. Singleton Design Pattern

8. Singleton not a singleton?

9. ATL Singleton and Singleton Class also from C++

10. Best approach - Opinons?

11. Menu programming approaches needed

12. A Different Approach


Powered by phpBB® Forum Software