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
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
The text was updated successfully, but these errors were encountered:
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
toprotected
? 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 meThe text was updated successfully, but these errors were encountered: