Hello Neil,



I previously mentioned that a progress indicator from the ICSA on the

status of a file being uploaded or downloaded would be welcome.



I had in mind that when an application requests a download or upload, it

provides it's name (e.g.: "AFTP") and as the ICSA displays status

messages on the ICSAWin box, they are also sent to the application that

sent the innitiate request in the form of commands (e.g.: "Status,

C:\Download\cpp.html, 24%").





To spare you searching trough the code (considering the point I still

know the system very well) I have also put togather the practical

implementation plan. 



1. When an application (in this example AFTP) requests an upload or

download the following line should be present (according to the

upload/download interface I use): 



	FromFileLoc "AFTP interface"



This line tells the ICSA which application is requesting the upload or

download and thus identifies which application requires to be recieving

the transfer status information.



2. The ICSA now indentifies where to actualy put the information by a

method that should already be present in the code in the ICSA that, on

innitialization of the ICSA checks the other program's serial numbers...

the code effectively sends the command sequence containing the

instruction "Lock" to the application who's serial number has a problem

via the same file that you will require to send the transfer status

information (in case it eases the locating of the code that does this

within the ICSA, the filename of the interface file is located by

looking in C:\FileLoc for a line beginning with "<program name>

interface =", in AFTP's case this would be "AFTP interface =" followed

by the exact path and filename of the POF file).



3. The format of the command containing the transfer status information

can be like the following (example for "C:\Download\cpp.html" on

"Win_Neil" at 24% done):



	---

	SET SOURCE = Win_Neil

	Status, C:\Download\cpp.html, 24%



This text would be appended to the file (located in #2). You can also

place error messages and anything the ICSA might have to say trough the

application in the future where there is currently "24%".



This would be all my programs would need. If the implementation the way

I described it is possible, tell me and I will make the small

adjustments on AFTP to make it compatible to that format, otherwise

let's discuss any problems.



P.S.: I am also attaching a number of updated versions of programs for

ICI, you'll see where to put them (in the distribution).



P.P.S.: I forgot to mention yesterday, there is something new to AFTP2.

You will notice there is an "Organizer" in the "New" menu, that

organizer manages a subsystem of databanks between applications. You can

drop files into AFTP's and other programs' databanks and they will be

automaticaly linked, but not phisicaly moved or copied anywhere. A

doubleclick to a file in the organizer window will show it in one of the

local windows currently open. You can also drag files from the organizer

window like from other sources and they will be copied into the

destination. Some applications (Streamer and PicFind currently) use the

standard format the AFTP's organizer uses to store links to files, so

AFTP can be used to organize files for those applications to use. Try it

and see.



			Observer aka DustWolf aka CyberLegend aka Jure Sah



C'ya!



--

Cellphone: +38640809676 (SMS enabled)



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

reply.



-=<{Spay and Neuter your humans to keep them off the streets and out of

Shelters!}>=-



The future of AI is in technology integration,

we have prepared everything for you:

http://www.aimetasearch.com/ici/index.htm



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