<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.12.3">
</HEAD>
<BODY>
You bet Barry.<BR>
<BR>
On Tue, 2007-04-03 at 19:50 -0400, Barry Siegfried wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">["(Skip) K8RRA" <<A HREF="mailto:k8rra@ameritech.net">k8rra@ameritech.net</A>> wrote]:</FONT>
>>SNIP<<<FONT COLOR="#000000"> bring them on!</FONT>
</PRE>
</BLOCKQUOTE>
See how I can bypass all the detail of above?...:-)
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Let's say I am in a system console client session that is connected</FONT>
<FONT COLOR="#000000">to my favorite Net/Rom node. I would like to sysop the node, reset</FONT>
<FONT COLOR="#000000">it and then connect again to load my initialization parameters.</FONT>
<FONT COLOR="#000000">Instead of typing all the initialization parameters manually, I can</FONT>
<FONT COLOR="#000000">instead have them stored in a file which I can then 'upload' to that</FONT>
<FONT COLOR="#000000">client session. The Net/Rom node command processor will receive them</FONT>
<FONT COLOR="#000000">line by line from my client connection and assign the values I want</FONT>
<FONT COLOR="#000000">to use for node initialization.</FONT>
</PRE>
</BLOCKQUOTE>
The example makes sense and my initial testing went well.<BR>
Except for the "*" to mark active session - it was missing here.<BR>
In *my* words - the UPLOAD command serves the same function as the SOURCE command: the SOURCE command is applied locally and UPLOAD is applied to the active remote host session.<BR>
<BR>
I'm beginning to think my initial thought about UPLOAD has a little merit.<BR>
Instead of trashing UPLOAD...<BR>
"UPLOAD <file>" should be replaced with "SOURCE <file> [<session #>]" syntax.<BR>
Because UPLOAD *should have* a <session #> parameter to remove ambiguity the work might be the same.<BR>
Before you nail me on the missing <session #>, consider doing your example to two remotes simultaneously.<BR>
Nothing about session structure prevents simultaneous remote connects.<BR>
That makes a lot more sense to me at this moment...<BR>
<BR>
Actually - I *might* be wrong about simultaneous sessions if they are *active* and receiving packets from more than one source... More later.
<BLOCKQUOTE TYPE=CITE>
<PRE>
</PRE>
</BLOCKQUOTE>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>