Hello Will,



I think I could be of help here...



Will Pearson wrote:

> I can't even begin to write the program until I have a complete specification of what the IOS can and can't 

> do and how it does it. Then and only then will I look at it and see if it possible to write something that 

> doesn't find too many false positives.



Currently the IOSC can:

A) Manage cluster/IPs

B) Use any number of Add-on functions

C) Help with user communication

D) Provide additional information



(A) is done by a standard of the diffirent IOS Consoles sending their

IP's, adding and removing them from a list of IPs via the IOS command

language. Each order to add or remove an IP can be either sent over the

Internet to other computers or fed into the local Console, it makes no

diffirence. In order to have a common set of IPs in the IP list, all

commands are cross-posted to every command parser in the cluster,

directly from the user interface.



(B) is possible because the structure of the IOS language. All messages

to the IOS Console itself are sent as messages to Function "SHELL". As

such, you can also send messages to any add-on function by addressing

the message to the function's textual name. IOSC communicates to the

functions using the Registry; each function has it's own record in the

IOSC's databank, where it is exactly described, where to should IOSC

write in the Registry.



(C) is just another built-in function. It is treated as any add-on

function and is called "USER". All parameters are sent to the user in

the textual format.



(D) is not even an extension. It is preformed by quick calls of one or

one group of SHELL function calls. The calls are made by clicking on a

button. Such are: Echo request (ping equivalent), Synchronize (make sure

IP lists match with the remote computer), Get functions (list add-on

function names) and Get version (verify what exactly is on the other

side).



Since IOSC currently communicates via UDP, it's communication is pretty

speedy: Only 1 second delay for an echo request (includes: send +

process + recieve, twice half way around the world). Atho TCP is known

to be a bit slower, I don't expect much of a diffirence.



--



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