Assume that I am working with the service in which large amount of data is to be sent.
If I apply this with WCF, will WBCF strangle the WCF on how much memory it takes for every service request? Or whenever I get a large number of hits in my service, will I get continuity in memory exceptions?
I am very excited to deal with this problem outside the WCF, I am still new to service development ...
While using binding features and reader, quotation like Andrew Green suggests that for the most practical uses, for an unlimited size, keep in mind that if you have long If you accept the running command then you will get other issues such as time Run in Mapti, it does not matter how it went created what services matter (WCF or not).
No matter what the size of your message is, the WCF service will need to be messed up for performance so that it does not flood. If you are hosting it in IIS or Vast, you will have additional built-in features for those features that will make your service even more "highly available". However, you still need to focus on concurrency issues The following WCF config provides an example of setting some throttling values.
& lt; System.serviceModel & gt; ... & lt; Behavior & gt; & Lt; ServiceBehaviors & gt; & Lt; Behavior Name = "Generic Service Manager" & gt; & Lt; Service TimeTime Transaction TimeTime = "00:09:10" /> & lt; ServiceException MaximagesConstruct = "20" MacScorts Sessions = "20" MaxConnectInstance = "20" /> & Lt; / Behavior & gt; & Lt; / ServiceBehaviors & gt; & Lt; / Behavior & gt; & Lt; /system.serviceModel> 
Comments
Post a Comment