design - Communication between client class library and web service / web service and server class library -
wondering others / best practice communicating between layers. question relates communication between layers 2-3 , 3-4.
our basic architecture (in order) follows:
- ui
- front end business classes
- web services
- back end business classes
- dal
the web services façade include logging , authentication end class libraries.
as such, web service passed request object includes parameters required web method along user credential (the user credential example stored in base class need pass webservice) , responds response objects (has things such status , message, if failed etc along object required) both request & response use custom generic class/or interface 1 result returned, otherwise class needs created.
sometimes makes sense response object @ layer 4 (though don't use request object unless lot of parameters need pasaws), in case have adapter class in layer 3 returns client. consistency have considered doing time, though think may overkill.
so iterate question, best practices communicating between layers? , should/do people use method outlined above (it works us) , should layers 3-4 implement similar method 2-3?
possible considerations:
- currently coded in house team of developers, client code may outsourced in future
- future web services wcf based (not sure if effects design other coding interfaces prefer anyway).
- we use .net
for sake of completeness:
it seems idea have response / requests in class library, way if want change web service wcf, there less work do.
Comments
Post a Comment