> *Subject:* Re: [twsocket] HTTP Tunnel
> We have a program that controls equipment. This program constantly
> sends log and error information to our supervisors room at our
> company so that any problem can instantly be addressed by one of
> our technicians. The connection is a TWSocket on the client side
> that connects to our server that uses a TWSocketServer to listen
> for connections.
> We now have a new client that refuses to open the port necessary
> for the equipment to log on to our server. However, http surfing is
> liberated. I would like to know the simplest solution to make a
> connection and pass the same data as always embedded in html.
Since you control the client and server, surely you can just update them to use
80 or 443 (TSocketServer has multilisten to support multiple IPs and ports) and
continue using your existing protocol.
If your customer has a proxy or firewall than insists on checking for the HTTP
protocol, use the web server component and PUT or POST your data, obviously more
work than adding an extra listener but not too hard.
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be