0

I am working on a 3-tier based website design using web-forms. With the basic layout of Presentation->Logic->Data.

Every class in each tier contains List<strings> Errors. So if an error happens on the Data tier, it can be copied to the Logic tier, and then exposed to the Presentation tier. The idea is to let the end user know an error happened and basic information on its location; logging will be used hand-in-hand for greater details of the errors for trouble shooting.

I have read of this parent-child style of error passing, just wondering if anyone has used this approach?

danday74
  • 52,471
  • 49
  • 232
  • 283
TheJoe
  • 57
  • 10
  • Presentation->Logic->Data sounds like a new way of saying MVC. I wouldn't describe this as a parent-child relationship. – danday74 Aug 23 '17 at 01:35
  • I think it is actually older. https://en.wikipedia.org/wiki/Multitier_architecture – TheJoe Aug 23 '17 at 13:17
  • The parent-child relationship is referring to the errors not the program design. – TheJoe Aug 23 '17 at 13:18
  • Noted by: https://stackoverflow.com/questions/10739914/what-is-the-difference-between-3-tier-architecture-and-a-mvc – TheJoe Aug 23 '17 at 13:30

0 Answers0