Databases
StackOverflow2013
Postsdbo
POmarking BLL classes as static or?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POmarking BLL classes as static or?
    primarykey
    data
    text
    <p>I already have a layered data access design which works well. But i dont know if it is the most suitable implementation or not.<br> i simply want to know that BLL classes or methots should be static or they should be concreate classes which has only one instance?<br> In the mean time i dont need to serialize BLL classes to use it in such a SOA design. But i dont know what the feature will bring.<br> Look at the following options:<br></p> <ol> <li>BLL classes and methots are static</li> <li>BLL classes are not static but its methots are static</li> <li>BLL classes are not static nor its methots. Application should create the BLL class everytime inorder to access its methots.</li> <li>BLL classes are not static nor its methots. But there is only one instance of each BLL class. And application uses these static instances inorder to use BLL methots.</li> </ol> <p>Which one is the most efficent mostly in performance and desing?</p> <p><strong>EDIT:</strong> <br><br> <strong>Option1</strong></p> <pre><code>public static class BllCustomer { public static List&lt;ModelCustomer&gt; GetCustomers() { } } // usage BllCustomer.GetCustomers(); </code></pre> <p><strong>Option2</strong></p> <pre><code>public class BllCustomer { public static List&lt;ModelCustomer&gt; GetCustomers() { } } // usage BllCustomer.GetCustomers(); </code></pre> <p><strong>Option3</strong></p> <pre><code>public class BllCustomer { public List&lt;ModelCustomer&gt; GetCustomers() { } } // usage BllCustomer bllCustomer = new BllCustomer(); bllCustomer.GetCustomers(); </code></pre> <p><strong>Option4</strong></p> <pre><code>public class BllCustomer { public List&lt;ModelCustomer&gt; GetCustomer() { } } // usage public static BllCustomer s_BllCustomer = new BllCustomer(); // whenever needed s_BllCustomer.GetCustomer(); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFer
    1. USFer
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POmarking BLL classes as static or?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POmarking BLL classes as static or?
      1. USFer
      1. VTBountyStart
    3. VO
      singulars
      1. POmarking BLL classes as static or?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy should people insist not giving an opinion to this issue, i simply can not understand. possibly, they can not see this topic in many other questions. yes i am talking to myself.
      singulars
      1. POmarking BLL classes as static or?
      1. USFer
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload