SCOUG-Programming Mailing List Archives

>> Next Message >>

Date:	Mon, 20 Apr 1998 16:12:34 PST8PDT
From:	MDINET!ELMONTE!TomE@mdipo.attmail.com (Emerson, Tom # GPS-MDI)
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com ('Scoug Programming list')
Subject:	SCOUG-Programming: Suggestion for next meeting's focus

Content Type: text/plain

At the SIG, Rollin mentioned he had created and nearly completed an FTP
server for OS/2. I think, for the purposes of investigating socket
programming and the like, that this would be an excellent subject, even
if it is a "run through of what he has already written", to show

1) how TCP/IP and sockets work "overall"
2) how to "spawn" processes and/or serve multiple clients
3) how to define and implement a "protocol" of commands, responses,
and "data packaging" [for instance, consider the idea of, say, "LZFTP" --
an FTP program that does on-the-fly LZ compression/decompression to
increase throughput]

Item #2, in particular, may be very interesting considering the
Unix/posix definition of "spawning" processes. Many Unix "daemons" use a
function called "fork", which simply creates a second instance of the
already-running program, complete with all variables AND OPEN FILES
intact (and in this case SOCKETS are considered "files"), then each
process continues on their merry way... As I said, however, this is the
"Unix" way of doing things -- is OS/2 the same or significantly
different?

Thoughts, comments, or criticisms?

Tom Emerson

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

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".

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

Return to [ 20 | April | 1998 ]

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.