🚀 go-pugleaf

"Vladimir Stefanovic" <spam@not.needed> wrote in message
news:41813ba0@newsgroups.borland.com...

> This was all related to LAN which was completely isolated
> from the internet. I'm just curious about techniques & princips
> of extending the system to work on internet.

There is no difference at all.  TCP is TCP regardless of whether it goes
over the LAN or over the Internet.  The Internet is nothing more than just a
world-sized LAN, afterall.

> How can I setup the system to do this (imaginary):

You should already have all of that, since it is exactly the same as over a
local LAN.

> 1) Connect to internet by laptop wherever (lets
> say in some foreign country)

That has nothing to do with TClientSocket, or even Borland, for that matter.
It is your own responsibility to provide an Internet connection to your
machine.  Whether that be via a dialup connection, or an ethernet
connection, or a wireless connection, or whatever.  That is handled at the
OS level, not your application level.  Once you have an Internet connection
established, TCP works exactly the same in your code regardless of the
connection type used.

> AFAIK, my company has E-mail server which is connected
> to internet, and has it's domain www.companyname.com.

So?  That is irrelevant to this discussion.


Gambit