When I encounter customer with such restrictions, I use my mobile hotspot for 
internet. I service a great many customers onsite in the LA area, and it’s been 
my experience that very few of them block traffic originating from within their 
own network. Health agencies and contractors are of course among them, and 
Government Contractors also have to enforce certain security restrictions 
depending on the information they have access to, in which case they typically 
also have Port Security, where if I plug my laptop into their network it will 
disable the port because I am not on the access list.

So there is always going to be security issues, and I can always get around 
them.

Bob S


On Feb 26, 2025, at 11:02 AM, Richard Gaskin via use-livecode 
<use-livecode@lists.runrev.com> wrote:

Bob Sneidar wrote:

Sockets are by nature a 2 way communication. After I write to a socket
I can read from that socket and get back whatever the receiver returns.
In fact the whole premise of what I am doing depends on it.

Yes, the socket connection is birectional, but establishing that connection 
requires two roles: someone has to dial the number (client), and someone else 
has to be sitting by the phone ready to pick up (server).

Both roles can be present on both sides, creating a system of peers. But a 
firewall will make reaching the listening app difficult, and a good firewall 
will make reaching that app impossible unless host-specific forwarding 
configurations are set up.  My most persuasive conversations on that with the 
IT staff at various orgs over the years have only reinforced my respect for the 
seriousness they bring to their work (in other words, when asked to have the 
org's firewall altered to support a departmental ad hoc usage, the answer is 
roundly "no").

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to