Nick, From what I can tell (Im connected to myself, and it gets confusing occassionally) the Checksum is only sent to the recipient. Is there any reasonable way to get the checksum sent to the sender as well? If not, its no big deal... I might be wrong about this whole thing anyway. Im still not completely comfortable with the Chat protocol/commands yet.
Also, Maybe something (although, It'd be sorta wierd and awkward) can be worked out with Auto-accept for files to(with the 'install to' path)...
(All these autoaccept things are my delusions of grandeur about completely automating a remote computer, sort of an overkill proxy) This way, can send/Install script files/plugins/etc... without having to just send a lot of #command Addtrigger type things.
You are right - the checksum is sent to the recipient, not the sender. I'm not sure what the sender would do with except nod sagely.
I'm a bit reluctant to have "auto-save" file names, they would be a big security hole if someone managed to change it to (say) windows\system and then send you a system DLL.
Actually, For sending along scripts/plugins/etc its all text. So, In theory, It can be done by making it into a big long textstream, and using an unused channel, and then the recieving client could just put the pieces back together.
That could just be a plugin of its own though, no reason to add it to Mushclient.
I noticed the lack of sender getting the checksums as well. It is basically used to verify the file was sent accurately, which is as important for the sender as it is the reciever to know.
Especially if the Sender doesnt know a lot about what theyre doing. You could be there for 10 minutes trying to get them to tell you if the checksums were the same (after explaining to them what they were looking for, etc)
Nod, mainly I just meant sending (outputting) the checksum information to both sides. This just tells the sender that everything has gone fine and that the file they thought they sent was sent correctly.
If I was sending a file and had this information, I wouldn't feel the need to get the remote side to review the file before really being sure it was sent correctly.
That whole warm fuzzy feeling would more quickly ensue.
Yes Nick, I had meant that both checksums were sent to either end. So that the sender, and reciever could see them, and do the visual check to make sure no problems happened.