Replies: 3 comments
-
|
Ok, I missed this discussion. Let me think about it and reply to this ASAP. |
Beta Was this translation helpful? Give feedback.
-
|
Custom settings are still can be access from SuperSocket/test/SuperSocket.Tests/MainTest.cs Lines 82 to 96 in d9d70f4 |
Beta Was this translation helpful? Give feedback.
-
|
If you want to have strong type access, I think you still have a way to do it. You can implement a your own service with the option type you want: YouOwnService(IServiceProvider serviceProvider, IOptions<YourServerOptions> serverOptions) SuperSocket/src/SuperSocket.Server/SuperSocketService.cs Lines 153 to 160 in d9d70f4 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I´ve started a SuperSocket 1.6 service conversion to 2.0 on Net 8 environment and I stuck on how to configure the ServerOptions to keep the legacy config the server is using. In 1.6, for each config file there´s some customer/tenant information besides the Ip/Port/SSl config, so a new ServerOptions is created passing this custom info into the Options parameters. Now In 2.0 this property has gone and I dont know how to keep those custom info on the new SuperSocketHostBuilder´s ConfigureAppConfiguration method.
Also, ServerOption is not accessed on UsePackageHandler (or in IPackageHandler´s Handle method when using a middleware) , so to accesss the customer/tenant information on each request is impossible.
So I like to know if some new features could be added on SuperSocket 2.0:
Thanks
AWS
Beta Was this translation helpful? Give feedback.
All reactions