wcf

How and when to dispose my objects?

由 大城市里の小女人 提交于 2020-12-27 03:17:37
问题 In my backend service I use unit of work pattern. I was wondering if I'm missing something related to disposing objects. First, this is the code I have so far, which works. The service just calls a request handler: [GlobalExceptionHandlerBehaviour(typeof(GlobalExceptionHandler))] public class CustomerService : ICustomerService { public void AddCustomer(AddCustomerRequest request) { ObjectFactory.GetInstance<AddCustomerRequestHandler>().Execute(request); } } The request handler looks like:

How and when to dispose my objects?

由 只谈情不闲聊 提交于 2020-12-27 03:15:15
问题 In my backend service I use unit of work pattern. I was wondering if I'm missing something related to disposing objects. First, this is the code I have so far, which works. The service just calls a request handler: [GlobalExceptionHandlerBehaviour(typeof(GlobalExceptionHandler))] public class CustomerService : ICustomerService { public void AddCustomer(AddCustomerRequest request) { ObjectFactory.GetInstance<AddCustomerRequestHandler>().Execute(request); } } The request handler looks like:

How and when to dispose my objects?

由 走远了吗. 提交于 2020-12-27 03:14:45
问题 In my backend service I use unit of work pattern. I was wondering if I'm missing something related to disposing objects. First, this is the code I have so far, which works. The service just calls a request handler: [GlobalExceptionHandlerBehaviour(typeof(GlobalExceptionHandler))] public class CustomerService : ICustomerService { public void AddCustomer(AddCustomerRequest request) { ObjectFactory.GetInstance<AddCustomerRequestHandler>().Execute(request); } } The request handler looks like:

How and when to dispose my objects?

由 a 夏天 提交于 2020-12-27 03:13:07
问题 In my backend service I use unit of work pattern. I was wondering if I'm missing something related to disposing objects. First, this is the code I have so far, which works. The service just calls a request handler: [GlobalExceptionHandlerBehaviour(typeof(GlobalExceptionHandler))] public class CustomerService : ICustomerService { public void AddCustomer(AddCustomerRequest request) { ObjectFactory.GetInstance<AddCustomerRequestHandler>().Execute(request); } } The request handler looks like:

WCF throttles requests

由 那年仲夏 提交于 2020-12-15 05:16:00
问题 I need to maintain an older service that's written in WCF. The issue is that when load testing the service, the requests appear to be throttled. On average each call takes around 250 ms on the server side. If I send one request, it completes in a little over 250 ms. If I send 10 requests, the first few complete right away and other requests are complete in seconds, where the number of seconds increases with the number of requests. I reproduced the issue in a simple project here https://github

WCF throttles requests

由 ≯℡__Kan透↙ 提交于 2020-12-15 05:15:10
问题 I need to maintain an older service that's written in WCF. The issue is that when load testing the service, the requests appear to be throttled. On average each call takes around 250 ms on the server side. If I send one request, it completes in a little over 250 ms. If I send 10 requests, the first few complete right away and other requests are complete in seconds, where the number of seconds increases with the number of requests. I reproduced the issue in a simple project here https://github

.NET Core 3.1 API Calling .NET Framework WCF Service secured using windows authentication (AD Group)

由 …衆ロ難τιáo~ 提交于 2020-12-15 02:43:45
问题 I am trying to call a .NET Framework WCF Service (which is secured by Windows Authentication using an AD group) from a .NET Core 3.1 API however I am getting the error message: System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate, NTLM'. The .NET Core API is hosted in IIS both on windows and the app pool that it runs under has a domain account

.NET Core 3.1 API Calling .NET Framework WCF Service secured using windows authentication (AD Group)

由 China☆狼群 提交于 2020-12-15 02:43:03
问题 I am trying to call a .NET Framework WCF Service (which is secured by Windows Authentication using an AD group) from a .NET Core 3.1 API however I am getting the error message: System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate, NTLM'. The .NET Core API is hosted in IIS both on windows and the app pool that it runs under has a domain account

.NET Core 3.1 API Calling .NET Framework WCF Service secured using windows authentication (AD Group)

由 对着背影说爱祢 提交于 2020-12-15 02:39:02
问题 I am trying to call a .NET Framework WCF Service (which is secured by Windows Authentication using an AD group) from a .NET Core 3.1 API however I am getting the error message: System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate, NTLM'. The .NET Core API is hosted in IIS both on windows and the app pool that it runs under has a domain account

REST easy with kbmMW #16 – Multiple servers using HTTP.sys transport

由 拈花ヽ惹草 提交于 2020-12-12 06:41:06
前文写过使用HTTP.sys转输层（TkbmMWHTTPSysServerTransport），实现一个kbmMW应用服务器。 如果在一台服务器上，同时运行多个，基于TkbmMWHTTPSysServerTransport实现的kbmMW应用服务器，该怎么配置呢？ 通常会遇到这样的错误信息，如：“Unable to bind to the underlying transport for … The IP Listen-Only list may contain a reference to an interface which does not exist on this machine.” or “Unable to open file….”. 其原因是Windows需要你来定义，允许服务器侦听的主机。仅仅将URL放在TkbmMWHTTPSysServerTransport组件的URL属性中是不够的。假设你的服务器有多个公共IP，你想基于一个公共IP来运行kbmMW服务器（Web服务器），这样的话，让其他的kbmMW服务器去侦听其他的公共IP地址。 在这种情况下，将url属性设置为Http://xxxx.y/,其中，xxxx是公共IP地址，y是端口号（通常为80）。但是，在尝试启动服务器之前，还需要告诉Windows，Http.sys去侦听该IP地址。
订阅 wcf