Neil Nelson wrote:

> I believe I have the IC SA ready enough for you to begin using. There

> is a little file transfer debug left but the time sync and send command

> appear to be working.  And I realized yesterday it would not take much

> to add a basic name vs. IP table for dynamic IP management.  The

> following describes the configuration and communication files for

> your review so that you can make any changes before I send you the

> program.

>

> Configuration File

> --------------

> min_cycle_time = 1000 /* File and socket command read cycle will not be

> less than 100 ms.

> icsa_comm_dir = C:\Programs\ICI\tcp\icic /* Local communications directory.

> ici_server_ip = 192.168.0.3 /* 66.51.195.107  First ici server ip

> number. Enter up to 5.

> ici_home_ip = 192.168.0.2

> local_server_port = 10101 /* Port number for local server activity.



Ahh I see. Can't wait to get my hands on the Console code downstairs. It

will be upgraded in no time.



> The above is copied directly from my working config file. The paramter

> name at the beginning of the line or at the left may consist of any string

> of characters not including spaces. Upper case may be used but all

> symbols in the name are changed to lower case for program use.

> 

> The equal sign is not required such that the first parameter and value

> may be entered as  'min_cycle_time 1000'.

> 

> The `/*' string means that everything from that symbol pair with a

> preceeding space, ` /*',  and to the end of the line will be discarded as

> being a comment.



My current Data Storage protocol does not know the " /*", but I suppose

I can add it (and remove the comments from the config file until this is

done).



> - icsa_comm_dir is the directory where local communication files are

> obtained and placed.  The string may terminate with or without a `\'.

> The file name used as input to the ICSA is currently fixed as

> 

> icsa.cmm

> 

> Later any number of files beginning with `icsa' will be detected and

> processed. File names used for output or local replies are currently

> named, e.g., as

> 

> ici_icsa



The solution is my Command Transfer protocol. Simply append anything

newer to the file and add a line with "---" at the start to seperate

multiple entries (recomended).



It would maybe be a good idea for you to use my Command Transfer

protocol in "ICSA.CMM" too so we can avoid the same problems there. If

you decide to do so, the Command Transfer xRead function solves another

set of problems by: 

1. Finding the first line with "---" in front

2. Record the file contents to a string

3. Stoping at the second line with "---" in front

4. Copying everything from #3 (that line included) to a Swap file 

5. Overwriting the current file with the Swap file

6. Deleting the Swap file



> - ici_server_ip will currently be the AIMetaSearch IP 66.51.195.107

> where the current ICI time (time sync) and the dynamic IPs are obtained.

> The number there now is my internal IP for that box.

> 

> - ici_home_ip will likely not be used for dynamic IPs since that IP

> will change.  I need to add the code to capture the IP at the server on the

> initial time-sync request and send it back, or capture it with the local

> ICSA.  I will look at that today.

> 

> - local_server_port is the port number of the local server routines.

> Currently all ICI programs should be using the same server port

> number.

> 

> This takes care of the config file. I will send a following email on

> the communications file.

> 

> Regards,

> 

> Neil Nelson





--



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



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

Http://WWW.MesonAI.Com

