"NewsGuy" <jo**@nospam.co m.auwrote in message
news:fg******** @news5.newsguy. com...
Hello I'm concidering better ways to architecture our VB.Net Webservices
project. Below is a draft of what I thought would be a decent way to go
about it, I was wondering about other peoples thoughts. I thought maybe a
half business object half dataset approach is feasable...Im not sure...
Teir1 - WebService
wsTblClient
Method Create()
Method Read()
Method Update()
Method Delete()
Teir2 - Business Objects
boBase
Method threadsafeCreat e()
Method threadsafeRead( )
Method threadsafeUpdat e()
Method threadsafeDelet e()
boTblClient
inherits boBase
Property dsTblClient
Property bindingSource
method untypeDS
method typeDS
Teir3 - Presentation
frmBase
frmClient
inherits frmBaseNormal
property BOtblClient
Im very noobie :(
Thank you so much for your time reading
John
Teir 1
UI
UI has reference to Presentation layer
Tier 2
Presentation or MVP Model View Presenter
Presentation has reference to Business layer
MVP consumes BL objects and methods.
Tier 3
Business Layer
Business Layer has reference Data Access layer
Method Create()
Method Read()
Method Update()
Method Delete()
Teir 4
Data Access layer
Method Create()
Method Read()
Method Update()
Method Delete()
What's the Web Service for? Is the Web service to be consumed by Windows
Desktop or ASP.Net solution.
This talks about MS Windows DNA a little bit, but there are other articles
too out on Google.
<http://www.c-sharpcorner.com/UploadFile/tavanover/NTierDevelopmen twithMS11130200 5054224AM/NTierDevelopmen twithMS1.aspx>
This link is about MVP you should look at the shows, and there are articles
out on Google about MVP.
MODEL-VIEW-PRESENTER
http://www.polymorphicpodcast.com/
click 'Shows'
click 'Design Patterns Bootcamp: Model View * Patterns*
view parts 1-5
Sorry man, because I am going to be blunt about it. What you have going on
there up above for architecture is some kind of a mess.
