SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 02 | March | 2000 ]

<< Previous Message << >> Next Message >>


Date: Thu, 2 Mar 2000 18:03:55 PST
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: TCP/IP socket programming ?

Content Type: text/plain

Steven Levine wrote:
>
> Localhost is just a alias name for your hostname / IP address.
>
> Take a look at the TCP/IP Programming Reference.
>
> There's a group of ports allocated for user defined
> use. Your applications will have configuration files
> to tell them which ip address/ports to listen and talk on.

Okay, I understand the hookup - thanks.

-- If I set Netscape to "localhost" instead of my mail server
(mail.duckyisp.net or whatever), then Netscape will try to communicate
with the mail port (25) on the machine that it's on.

-- And if my monitoring module is watching that port, then it will get
all mail requests from Netscape and can take care of them (and can also
open port 25 on the non-local mail server machine and forward to it the
requests from Netscape, thus making my monitoring module "invisible").

-- If I have more than one monitoring module in series (like a string
of command line filters), then I either have to tell them what ports to
use or the monitoring modules need some supervisorial routine that will
dynamically tell them what ports to use.

Yes?

I went to IBM Redbooks but couldn't find the TCP/IP Programming
Reference you mentioned (searched on "tcp/ip programming"). Where is
it?

Thanks, Steven.

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 02 | March | 2000 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.