You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Allowing ServerOptions to be extended to include some custom info;
Accessing ServerOptions on a multile server instances configuration, allowing to access the correspondent server instance custom config on packet handler/middleware.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
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