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 need a way to run an http listener in .net and receive websocket connection. I specifically want to do this to use a .net application with a browser frontend, and in particular, i want to make it fully cross platform including both desktop and mobile device.
I have read some discussions where httpListener was deprecated and .NET is now only supporting Kestrel. Kestrel is crossplatform, but its also housed in the giant asp.net ecosystem. I don't know if its even possible to separate Kestrel from the giant conglomeration of memory-hogging asp components to make something lightweight.
I have seen a few projects off the radar (like Ouii) attempting to pioneer real browser frontends with websocket backends. But Ouii is overengineered and does a poor job of presenting itself to beginners. It also uses XAML and tries to accomplish way too much.
React, Blazor, Elm, Flutter, and numerous other architectures have demonstrated that you can very easily build your own component-UI system. You don't need someone to give you a framework to do it. But for some reason the world is completely mislead by these enormous overengineered frameworks.
I'm looking for a simple .net websockets listener that will run on android, linux, mac os, ios, windows. JUST a listener to support a websocket connection. That would make so many things possible. Where can I find that?
As an aside: The deprecation of httpListener met with a lot of rejection but only from a tiny group of off-the-radar developers. Someone following Ouii spoke up about how it would require them to move to the much bulkier Kestrel and ASP.NET system. It looks like Microsoft is going out of its way to keep everyone on the asp.net and xamarin trains and not actually offer a lightweight solution because they know it would undermine the market for these other technologies. Only an open source cross platform websocket listener will really move the HTML UI forward.
The text was updated successfully, but these errors were encountered:
So here's what I have been researching:
I need a way to run an http listener in .net and receive websocket connection. I specifically want to do this to use a .net application with a browser frontend, and in particular, i want to make it fully cross platform including both desktop and mobile device.
I have read some discussions where httpListener was deprecated and .NET is now only supporting Kestrel. Kestrel is crossplatform, but its also housed in the giant asp.net ecosystem. I don't know if its even possible to separate Kestrel from the giant conglomeration of memory-hogging asp components to make something lightweight.
I have seen a few projects off the radar (like Ouii) attempting to pioneer real browser frontends with websocket backends. But Ouii is overengineered and does a poor job of presenting itself to beginners. It also uses XAML and tries to accomplish way too much.
React, Blazor, Elm, Flutter, and numerous other architectures have demonstrated that you can very easily build your own component-UI system. You don't need someone to give you a framework to do it. But for some reason the world is completely mislead by these enormous overengineered frameworks.
I'm looking for a simple .net websockets listener that will run on android, linux, mac os, ios, windows. JUST a listener to support a websocket connection. That would make so many things possible. Where can I find that?
As an aside: The deprecation of httpListener met with a lot of rejection but only from a tiny group of off-the-radar developers. Someone following Ouii spoke up about how it would require them to move to the much bulkier Kestrel and ASP.NET system. It looks like Microsoft is going out of its way to keep everyone on the asp.net and xamarin trains and not actually offer a lightweight solution because they know it would undermine the market for these other technologies. Only an open source cross platform websocket listener will really move the HTML UI forward.
The text was updated successfully, but these errors were encountered: