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 [ 16 | August | 1998 ]

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


Date: Sun, 16 Aug 1998 18:20:51 PDT
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: FTP Server spec

Content Type: text/plain

Hi Rollin,

Got both your responses through this list, thanks.

> > 5. What functionality is available in other FTP servers ...
> I don't think any of them will affect our design that much. ...

Agreed. I don't see any design changes.

> Support of other protocols (like TFP and HTTP)

What's TFP?

> ... random i/o should be supported by a well written Read/Write file.

But the command must specify a random read or write. RFC959 specifies a
RESTART command, but it isn't robust enough to be used in this
situation. I suggest an extension command (RANR, RANW?), or at least a
command extension (to RETR and STOR).

> > RecordFileTransfer *****What is this method for?
> Logging the fact that a transfer took place
> (I think we called it long term statistics).

Okay, thanks.

> > *****Where do all the extension commands go?
> Actually, I was thinking of an Extension module. If a command is not
> recognized, it can be passed to the Extension module. This module
> would be responsible for registering and communicating with
> user exits and other FTP extensions.

Yes, better than what I was thinking of. (I was thinking of a Command
module that calls the RFC959 module, but that doesn't allow for
extensions to the RFC959 commands unless you then also extend the RFC959
module!)

Should all extensions go in one module? Would a CommandExtension module
plus a UserExitModule be a better way to go?

> >Module: Server
> > GetConnection *****This handshakes when 21 says "hi", yes?
> And returns a handle to that connection.

Okay, thanks.

> > DispatchConnection *****What does this method do? Where's the
> >rollover?
> Creates a new thread and appropriate objects to handle the new connection.
> What do you mean by rollover?

Where control rolls from GetConnection to DispatchConnection. It wasn't
clear from the names what each module was doing. DispatchConnection
takes over as soon as there's a handle so GetConnection can go back to
paying attention to StartListen, yes? This keeps GetConnection from
being tied up when simultaneous signons occur, yes?

Question for the teacher: Why can't GetConnection and
DispatchConnection be combined?

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

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


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

Return to [ 16 | August | 1998 ]



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.