SCOUG-Programming Mailing List Archives

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

Date:	Fri, 29 May 1998 08:13:04 PST8PDT
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com
Subject:	SCOUG-Programming: Design guidelines

Content Type: text/plain

Rollin White wrote:

> As I searched high and low for FTP
> servers, I found many choices, but each of them had a fatal flaw.

What, typically, did the coders miss or mess up?

> I asked
> myself what it would take to write my own FTP server. I examined the
> appropriate RFCs

I'd like to look at those RFCs (they're at
ftp://ds.internic.net/rfc/rfc####.txt). Do you still know the 4-digit
RFC numbers?

> Sockets can be connected to
> two processes on the same machine or different machines. Sockets are connected to a
> specific port(or port number) on a given machine.

I understand that a socket is connected to a "soft" port for network
communications. I don't understand how a socket can connect to two
processes on the same machine since there's only one socket to plug
into, unless you just mean that the two processes use the same socket.
Is that it?

> Another Unix related issue was the representation of paths and drive
> letters. In Unix, there are no drive letters.

How do you access drives in Unix? With a number? Or is the Unix file
system very different (spanning, etc.)?

> (I like specifying the drive letter as the top level subdirectory, i.e.) "CD /d/tmp".

That's good. I already use such a system.

> These two issues (paths/drives and security) lead to very complicated handling of directory names
> and references - an issue that I did not foresee, and a module that
> could use rewriting.

What those complications are would be good for a lesson.

> A command string
> is retrieved and broken into its parts (the command and optional
> parameters).

Is this where GetString() comes in?

> Another key concept is a Command Structure which holds all of the
> information about the connection and the command. This structure is
> passed around to all of the Handle functions for manipulation.

This would be good for a lesson. Can you throw the Command Structure at
us without comment at this time, so we can see what's in it and ponder
how to use it?

And an overall question. What compiler should we use? I have VisualAge
C/C++ and Watcom C/C++. Any pros/cons?

- Peter Skye

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

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 [ 29 | May | 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.