why do you need a webservice to persist data? security, validation or
something? in distributed solutions this can be a big time bottlneck.
i general abstract my communication layer (web services, remoting,
enterprise services (server apps)) from actual logic. In short, I'd have
another class do the persisting.
ice
"Sam Santiago" <ss*******@n0spam-SoftiTechture.com> wrote in message
news:OQ**************@TK2MSFTNGP14.phx.gbl...
Depending on the complexity it can either talk to the DAL or simply use
any Business Objects you may have to perform the required business
functionality. Check out this link:
Designing Applications and Services
http://msdn.microsoft.com/library/de...AppArchCh2.asp
Thanks,
Sam
--
_______________________________
Sam Santiago
ss*******@n0spam-SoftiTechture.com
http://www.SoftiTechture.com
_______________________________
"Alexander Kaplunov" <ak*******@nvidia.com> wrote in message
news:eR**************@TK2MSFTNGP10.phx.gbl... I have a web service which accepts some data and stores that data in the
database. My question is should this web service talk directly to the
data access layer (DAL), which populates the database or should there be an
extra layer between web service and the DAL? If there should be an extra layer
then what is that layer?
Also, if you have any link to sites that cover these type of issues I
would appreciate it if you could share them.
Thanks,
Alex.