"Harold P. Boushell" wrote:

> With Jure's help "WE" will be able to deliver TRUE

> P2P with dynamic IP management.  This would still

> require a SERVER IN THE MIDDLE, however, that is only

> required long enough to make the PROPER INTRODUCTIONS

> between WORKSTATIONS.  After the introduction the

> SERVER can with draw from the TEMPORARY SESSION PROTOCALL.



Ahem ahem. Ok, the servers in the networks forming Internet are logicaly

needed, but also, if both parties have dynamic IPs, a computer with a

fixed IP is required to indentify eachother on connection

enstablishment, then the third party can be droped from the cluster

(note that if a dynamic IP refers to a fixed name like

"www.mesonai.com", there is no such problem, because such can be entered

instead of the numeric IP [atho IOSC automaticaly converts them to

numeric versions, to fit the standard]).



There is no problem in using Neil's Linux IOS server to enstablish such

a connection --> a trip for an IOS synchronization procedure (connection

enstablishment) from my computer to it (half way around the world) is

less then 1 second.



> The COMMAND structure as I see it for the IOS

> utilizing the communication structure between

> WORKSTATIONS, SERVER and OTHER (not me) dynamic

> IP address.  On WINDOW's BOXES the following

> commands syntax will be necessary in order to

> keep things utterly simple.  There are only

> three types of delimiters for the command

> structure and they are { # = , } that is

> POUND SIGN, EQUALS, and COMMA.  The POUND SIGN

> is the start of a COMMAND.  The COMMA is the

> COMMAND terminator.  The EQUALS SIGN is used

> to start a STRING of attributes for a given

> command.  This string of attributes will include

> such things a FILENAMES.exe, .com, .bat,.

> 

> The commands under consideration are:

> 

> #DIR, #CLS, #C_DIR, #MKDIR=anything.123,.

> #CLEAR_HEADER., #DISKVOLUM=PUBLIC_DIRECTORY00,

> #COPY_C:\TEMP0$.TXT=D:\WINNT\SYSTEM32\DRIVERS\EPSON740.DRV,

> #READ_C:\TEMP9$.TXT=DA$(0),



Good. Pick a name for this function, I'd say "Command", would be ok. So

it is called like "1.2.3.4 local-command: #DIR," in bare code.



Harold, also keep in mind on an implementation of the same thing in

"Remote" format, when an undefined group of computers is used to, for

example, backup a set of files, in a cooperative effort (for example if

I backup a folder of 20 files to 10 computers, they split the file

numbers in a way that each file is, for example, duplicated only twice

in the entire group). You can use the IOS Console's abbility to process

"Task_grabed" messages, that are sent to the entire cluster and have the

original command added for reference.



It is not a "must", but it kind of goes well with the principles we were

holding onto at the begining.



C'ya!



--



Don't feel bad about asking/telling me anything, I will always gladly

reply.



Digging for info? Try AI Meta Search:

Http://WWW.AIMetaSearch.Com



GTSC4 -- If nobody else wants to do it, why shouldn't we?(TM)

Meson & GTSC4 are now merged:

Http://WWW.MesonAI.Com

