ABThe same web server with different web applications. There is a
ABlittle possibility that a client windows application will be built
ABto be used from a remote computer.
AB>
ABThe website admin For the administration of legal forms for admin,>who is using them,
ABNews, events, audio and partially the legal forms for customers. The
ABcustomers will use it for the legal forms for customers. The rest of
ABit like membership/profile providers would be used by the internal
ABweb application system to provide access to these different parts.
well, so it's role-based system
ABproject would be restricted to its own data store and the access to>do they have the same rights
ABthings would be limmited to
ABFor an example, the Audio service
ABwould not need to know what is going on with the services for legal
ABforms. Using the Audio service example, It would need access to a
ABdatabase with membership provider, its own database to store audio
ABrelated information and it would need to have access to the
ABapp_data folder of the project that makes use of the audio service.
It sounds that it's better to create different webservers, because it simplifies
you the setting security for each of them
ABJust trying to be more organized with the code. Why would you want>You should consider this by "why I want to split them" ?!
ABmethods for an Audio service located in a membership service? Well,
ABok not the best example, will try this again. Why would you want to
ABmix methods for the Audio service with the methods from the News or
ABevents services? They are totally unrelated for one, and it makes it
ABeasier for me to know what service/section of the service to jump to
ABif they are divided into multiple services.
exactly. split them logically and extract common stuff to the separate assembly
shared amont them
ABWhat do you mean by this? See abovwe. Unless there are too many
ABrisks/performance problems with dividing the services up into each
ABtask type...Let me know if there are any?
if you are not going to end up with the 100 webservices I wouldn't consider
performace issues there
---
WBR,
Michael Nemtsev [Microsoft MVP] :: blog: http://spaces.live.com/laflour
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo