Tim,
I wouldn't say the tiers are very cleanly separated, but I'd say it's has
three layers.
The data tier is well identified ...it's basically all the stored procedures
in the Portal Database. Now, any file that ends with DB in the Component
folder is also part of the data layer...there's no business logic in them
from what I can see.
Now, like most ASP.Net applications, the business and presentation layers
are really blurred....normally this happens because people stuff their
business layer in codebehind files...but with IBuySpy, it's such a basic
thing that the busisness layer is really really thin..so it's hard to
properly define it. Things in the component folder which don't end in with
DB are all part of the business layer. In addition, I'm sure there's some
stuff in the code-behind files which also is part of it.
The presentation layer is all the aspx files, and anything in the
code-behind which isn't business logic - that code that behaves against the
presentation and not the business.
The best architectured ASP.Net application I've seen, and based my own
programming on, is the ASP.Net 2.0 beta...it's now fully released and named
CommunityServer..haven't looked at the final source code:
http://www.telligentsystems.com/Solutions/Forums/ pretty damn complicated
stuff though..
HTH,
Karl
"Timothy V" <tr****@msn.com> wrote in message
news:OH**************@TK2MSFTNGP12.phx.gbl...
Hi,
I was wondering what tier-architecture is IBuySpyStore?
Depending which one, can someone explain which parts belong in which tier?
Thank you very much in advance,
Tim.