Specifically what we are trying to 'demystify' is this: We created a wcf service that we allow other developers to consume. However lets say with the default wcf settings one of the developers consums the service, runs a loop that consumes 10 connections and never calls .close() on the service... Basically this keeps anyone else from being able to use the service... thus the real question is: How do you keep a developer that is consuming your service from being able to completely bringing it down and making it unusable for everyone? How is it even possible to create a wcf service that works like a web service? ie: we never have to worry about inside/outside developers consuming our service and using up all of the connections. The feeling we are getting is that you could not use wcf to expose data to outside entities like you could a web service out of fear of that company/developer not calling the .close() method. Any help/insight would be appreciated.
How does Publisher tie into all of this? -- JoAnn Paules MVP Microsoft [Publisher] Tech Editor for "Microsoft Publisher 2007 For Dummies" "aiKeith" wrote in message news:4CD03FB4-2DA0-47BE-AC3F-714B8F1CDA6E@microsoft.com... > Specifically what we are trying to 'demystify' is this: > > We created a wcf service that we allow other developers to consume. > However > lets say with the default wcf settings one of the developers consums the > service, runs a loop that consumes 10 connections and never calls .close() > on > the service... > > Basically this keeps anyone else from being able to use the service... > thus > the real question is: How do you keep a developer that is consuming your > service from being able to completely bringing it down and making it > unusable > for everyone? > > How is it even possible to create a wcf service that works like a web > service? ie: we never have to worry about inside/outside developers > consuming our service and using up all of the connections. The feeling we > are getting is that you could not use wcf to expose data to outside > entities > like you could a web service out of fear of that company/developer not > calling the .close() method. > > Any help/insight would be appreciated.
LOL, LOL - well i used to post in there no problem, now when i choose 'where to post' all i get is a VERY LONG dropdown list of UNALPHABETIZED options. I choose one that just said 'DEVELOPER' --- so i now have no way to post in the right spot. sorry... "JoAnn Paules" wrote: > How does Publisher tie into all of this? > > -- > > JoAnn Paules > MVP Microsoft [Publisher] > Tech Editor for "Microsoft Publisher 2007 For Dummies" > > > "aiKeith" wrote in message > news:4CD03FB4-2DA0-47BE-AC3F-714B8F1CDA6E@microsoft.com... > > Specifically what we are trying to 'demystify' is this: > > > > We created a wcf service that we allow other developers to consume. > > However > > lets say with the default wcf settings one of the developers consums the > > service, runs a loop that consumes 10 connections and never calls .close() > > on > > the service... > > > > Basically this keeps anyone else from being able to use the service... > > thus > > the real question is: How do you keep a developer that is consuming your > > service from being able to completely bringing it down and making it > > unusable > > for everyone? > > > > How is it even possible to create a wcf service that works like a web > > service? ie: we never have to worry about inside/outside developers > > consuming our service and using up all of the connections. The feeling we > > are getting is that you could not use wcf to expose data to outside > > entities > > like you could a web service out of fear of that company/developer not > > calling the .close() method. > > > > Any help/insight would be appreciated. > > >
