Our team is looking into integrating a Halibut server into an existing Asp Net application. The hosting model of this application is a bit restrictive so we would like to use the existing iis server if possible. I have created a fork and tested accepting websockets from the Asp Net Owin pipeline, but I would like to keep Halibut updated without maintaining a fork.
Would you consider changing the internal HalibutRuntime ctor, ExchangeProtocolBuilder, HandleMessage, HandleMessageAsync to protected? Then I could simply inherit the HalibutRuntime class and maintain type safety. I could work around this by using reflection, but that seems a bit to brittle for me
Our team is looking into integrating a Halibut server into an existing Asp Net application. The hosting model of this application is a bit restrictive so we would like to use the existing iis server if possible. I have created a fork and tested accepting websockets from the Asp Net Owin pipeline, but I would like to keep
Halibutupdated without maintaining a fork.Would you consider changing the
internal HalibutRuntimector,ExchangeProtocolBuilder,HandleMessage,HandleMessageAsynctoprotected? Then I could simply inherit the HalibutRuntime class and maintain type safety. I could work around this by using reflection, but that seems a bit to brittle for me