469,578 Members | 1,314 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,578 developers. It's quick & easy.

Re: More than 1 web service?

Hello Andy,
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>
>who is using them,
ABThe website admin For the administration of legal forms for admin,
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
>do they have the same rights
ABproject would be restricted to its own data store and the access to
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
>You should consider this by "why I want to split them" ?!
ABJust trying to be more organized with the code. Why would you want
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
Jun 27 '08 #1
1 1239
So, the basic conclusion is that it would be best probably to create a WCF
service project and create different services in that project for each task
that the web applications need to complete... Just making sure I get the
final line before starting...
"Michael Nemtsev [MVP]" <ne*****@msn.comwrote in message
news:90**************************@msnews.microsoft .com...
Hello Andy,
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>
>>who is using them,
ABThe website admin For the administration of legal forms for admin,
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
>>do they have the same rights
ABproject would be restricted to its own data store and the access to
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
>>You should consider this by "why I want to split them" ?!
ABJust trying to be more organized with the code. Why would you want
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

Jun 27 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Jorge Ribeiro | last post: by
3 posts views Thread by Tim Zych | last post: by
15 posts views Thread by Bill Fuller | last post: by
6 posts views Thread by AAAAA | last post: by
reply views Thread by suresh191 | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.