Neil Nelson wrote:

> I am sorry I missed you. 



No problem I was just on for a while also doing other things.



I have since worked on other ICI software: 



The AFTP2 program now has a bunch of commands in it's menus that will

automaticaly align windows in the display (for example: 2 remote

browsers and a local browser or a local and remote browser with an

organizer, etc) as you have asked for. There is also a command to

minimize all windows, which in combination with the auto aligning

enables the user to set his AFTP2 workarea into order in no time.



I have also worked on the SysBridge program, which I would preffer to be

testing for a while before adding it to the compliation, since some of

it's new features might be annoying rather than usefull. In addition to

the previous beeping when system configuration changes, the new

SysBridge also has the abbility to display a notification window when a

certian event occurs (for example system time changes or a new CD is

noticed in a CD drive). It also now changes the ICI pulse to a standard

low value when the system goes to low-power mode (which is then set back

to the previous value when the system resumes normal power mode). There

is compatiblity between Plug and play systems and ICI trough SysBridge,

since when a device is plugged into the computer, it's status changed or

removed, SysBridge can automaticaly execute an ICI command from it's

"AutoStart" databank. Also available for future programming is that any

procedures are executed when other system configuration changes. 



Say if the ICSA needs any of such, for example I don't know, perhaps

automaticaly disconnecting all users when system before goes into

suspend (that would be a good idea since programs do not run durring

suspend mode and ICSA connections are likely not to timeout then) if so

it would be likely a good idea to get a return command (or echo) from

the ICSA that the system is ready to suspend (SysBridge is able to delay

or cancel the automatic system suspend procedure), since the suspend

procedure is a short process and the ICSA might not get the chance to

execute the disconnect in time.



> I was out shoveling grain.



Interesting.



> It sounds like what you mean is that you want to close the socket

> if a message is not authenticated or if there is an encryption error,

> which seems like something easy to do.



Yes I was thinking in that direction. Of course it would be good if you

consider the options: Will the abbility to infinately try a connection

before a command injection is succesfull be more of a security risk than

the constant disconnecting of the user in question? In my view of it, it

is a security risk big enough, but then again I do not know what

information is being sent around durring a connection enstablishment and

how much of a security risk is in repeating that. Perhaps add it as an

optional feature?



P.s.: For AFTP2 I could use the format in which it is notified about

download status.



P.p.s.: Harold has been notified regarding the few points you've sent me

previously, but has not replied since.



			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.



"Yes, Master."



Have you been told Internet will always be

threatened by worms viruses etc? We don't think so:

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



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