Also bear in mind that if your app listens with a socket then users may be presented with a dialog to allow internet connections for that app. Some users won’t like that.
It listens just once, at startup, to localhost, and having connected does not listen again.
Yes, but they still get the message. I had the same idea with my components and my alpha test got backlash.
Which platform, and does it happen at every launch of the app or just when it’s run the first time?
If I remember correctly, Windows would ask on first launch (but not subsequent launches) and macOS was asking on every launch. I don’t recall what Linux users reported as there are so few.
Either way, the issue was that they don’t want an app that shouldn’t be connecting to the internet popping up and asking to connect to the internet in this manner. When they say no because they’re security conscious, then the app breaks.
Mmmm. I need a way for an HTMLViewer to communicate to the rest of the app. My options for doing this keep shrinking, apparently.
Chunk the data through the event. I spent a lot of time looking for alternatives and there aren’t any without major caveats.
Been there, done that. Works reasonably well for macOS and IIRC Linux. But under Windows, each chunk was taking 200msec or so. You only need a few k of data for that to become too slow.
Oh, I know. I have two data-heavy components built this way, but it is what it is.
OK, @ and I have been messing with this. Using the loopback interface doesn’t popup the firewall dialog on Windows 10. Will be re-testing on macOS shortly.
Just finished my macOS test, and this appears to be working flawlessly there without the requests for permission. I still see them getting messages from apps like Little Snitch, so be sure to code a fallback so that your app doesn’t break if they deny in a third-party firewall and you should be good to go.
Now just be sure you don’t leave any holes that can be exploited.
I made a <https://xojo.com/issue/56420> for the CPU usage issue.
Thanks for the reports that use of the loopback (“localhost”) does not trigger a demand for my inside leg measurement. Barmy it would have been, but then OS vendors have been fairly barmy of late.