Possible FCP options on a ClientGet: offline=true // keep going after this connection closes persist=false // don't keep going after the node is restarted remember=false // don't remember after completed => won't show up on ListRecentlyCompleted (only valid if offline=true) remind=true // if the conn is open, or a later conn with same client name, tell me when it has completed, or on connection. requires clients to have a unique Name.
returnType: - direct // send over FCP, all at once. not valid unless offline=false, persist=false, remember=false - cache // don't return at all, just fetch to cache. aka prefetch. - chunked // return in segments as available, out of order, for advanced FCP clients - cdisk // write to a file, name provided by client, will be renamed at last minute, client may provide temp name - ndisk // write to a file, node creates filename - temp // store in encrypted temporary space on the node, for later retrieval onCompletion=<optional script to run> There are commands for reconfiguring the node, and for shutting it down. Saving data to disk in specified locations, reconfiguring the node, shutting it down, or running scripts, are all sensitive; we can have a simple password hash in the freenet.conf to authorize such things, and another flag for a blanket ban. (freenet.conf should not be world readable, and since we will often be writing it, we can ensure that it isn't). Remote users should be using ssh -L anyway; password auth is simply to cater for the paranoid. -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20060126/b5ce854f/attachment.pgp>
