You searched for the word(s): userid:47454

More Search Options

RSS Available

• Re: N-Tier Application?

  how to separate the business and UI layer Introduce an application server. So... Web Server tier runs presentation layer. Application Server tier runs business layer and data access layer. Database Server tier is your data. Your code-behind pages can call the application server through remoting or web services. Depending on your scalability and infrastucture requirements, introducing this midtier may be overkill and you might be better off just leaving the business layer running on the web server

  Posted to Architecture (Forum) by dfoderick on 12/8/2005

• Re: N-Tier (3 tier, in this case) design, best method (check out what I have so far)

  Something about putting SQL logic in the Business layer doesn't seem ideal. Exactly right. You can use the Repository design pattern to separate your business logic from data access logic.

  Posted to Architecture (Forum) by dfoderick on 11/23/2005

• Re: Business entities with CRUD.

  I haven't tried using char[] instead of string. Off the top of my head I would say it is going to be a major pain. It is always better to double check everything coming from the presentation layer in the business layer. Many back end programmers view the client as an untrusted tier. Property setters or some PreSave method seem like logical places to put those validation rules. Some shops put the length of a string property in an attribute. The UI can reflect over the length attribute on the business

  Posted to Architecture (Forum) by dfoderick on 10/26/2005

• Re: Business entities with CRUD.

  Is it OK for the presentation layer (the client) to call insatnce methods of the repositories to get business entities? One more note on this: security and scalability are two reasons for abandoning client/server and going to an application server model. If the responsibilites of your layers are correctly aligned then its easier to do.

  Posted to Architecture (Forum) by dfoderick on 10/21/2005

• Re: Business entities with CRUD.

  is there any reason why you favor instance methods? No specific reason in regards to repositories, its just that a class with a lot of static methods on it is a code smell. You can get the same ease of use by just creating a singleton (a static reference to an instance object) without creating static methods on the object instance. public static LoanRepository Loans = new LoanRepository(); where LoanRepository has no static methods. Then just call Loans.GetLoan(loanNumber) anywhere in your code.

  Posted to Architecture (Forum) by dfoderick on 10/20/2005

• Re: Business entities with CRUD.

  the three put together would constitue 1 tier and the 2 remote databases would be a tier each is it? For counting tiers, just count the types of machines on your network. It sounds like you have clients and database servers. That makes two tiers. Client/Server. my presentation layer would call either static or instance methods of the classess in the repository which would in turn invoke the DAL and return the populated entities or a collection of them. is that a correct statement? Exactly. Favor

  Posted to Architecture (Forum) by dfoderick on 10/19/2005

• Re: Business entities with CRUD.

  Repositories are not DAL. Repositories are a thin layer at the edge of your domain to decouple your entities from whatever persistence mechanism you are using. So, Presentation => Repository => DAL These are application layers not tiers. How you distribute the layers amongst nodes on your network is a separate aspect. If you are using n-tier then you would most likely introduce a service layer above the repository which would act as a remote stateless facade for the repository.

  Posted to Architecture (Forum) by dfoderick on 10/19/2005

• Re: Are Repositories still needed when using ORMs?

  http://patternshare.org/default.aspx/Home.DDD.Repositories

  Posted to Architecture (Forum) by dfoderick on 10/19/2005

• Re: Are Repositories still needed when using ORMs?

  ALFKI, You misunderstand the Repository which has caused you to implement the pattern incorrectly (I know because I made the same mistake initially too). You create a Repository for each Aggregate Root in your domain, not each entity. There will only be a handful of aggregage roots in your domain (generally). Thus if you have Order and OrderDetails entities, you create only an Order Repository. You do not create one for OrderDetails. Depending on your domain, you might have Customers and Orders and

  Posted to Architecture (Forum) by dfoderick on 10/18/2005

• Re: Object versioning

  We do something similar where I work. For example, instead of a simple boolean property we have an AuditEventCollection. This collection keeps a history of changes to the boolean value including who and when they changed it. So instead of a simple true/false we have these methods on the collection. Loan.IsComplete.IsSet() => check to see if the boolean value is true Loan.IsComplete.GetLastEvent() => gets details of who and when the last value was set Loan.IsComplete.Set(user) => sets the

  Posted to Architecture (Forum) by dfoderick on 10/18/2005