Yusuke Fujiwara

解析と回避策の提示ありがとうございます。まずは回避策を適用して進めたいと思います。

Sorry, I found the design bug that `ResponseContext` is not reused correctly, so it leads pool exhausion. So we should add the mechanism to reuse the `ResponseContext` when we have...

Sorry for poor documentation and missing samples... You can solve this with putting following lines: ``` c# // Configure using "def" for ServiceTypeLocator configuration.ServiceTypeLocatorProvider =s => def; // Prevents method...

Sorry, there are no public APIs to use custom serializer other than msgpack. 2014-07-28 18:18 GMT+09:00 sburnicki [email protected]: > Hi, > > is it possible to use this framework but...

I found that this is a limitation from [Windows API design](https://docs.microsoft.com/en-us/windows/win32/api/wincred/ns-wincred-credentiala), it says that: > `CredentialBlobSize` > The size, in bytes, of the `CredentialBlob` member. This member cannot be larger...

+1 I think that a combination of Functions Proxy with Easy Auth enables modern secure auth layer in front of the apps without any coding. It really helps securing apps...

Sorry for delay, but it had been already supported. https://github.com/msgpack/msgpack-cli/blob/e6b43e4f82cd529dc1dd6f2086324a32db2cbe83/src/MsgPack/MsgPack.csproj#L7 Any problem in Blazor?

Sorry, I missed this issue. Specify types as rest arguments like following: ```c# SerializerGenerator.GenerateCode( new SerializerCodeGenerationConfiguration {...}, typeof(Foo), typeof(Bar) ) ``` Note that you can specify types as `IEnumerable`, so...

I cannot repro the issue. Coud you tell me testing environment? My environment is Windows 10 Pro X64 AU, Core i7-3770, 16GB RAM, .NET 4.6.1 build with CLR 4.6.2, release...

I got it. Do you mean `MessagePackSerializer.Get()` should be over 10x than now?