On Wed, 25 Feb 2015, Michiel van der Vlist wrote to mark lewis:

 MvdV>> In my mind there is no doubt: Let the *.req file initiate the 
 MvdV>> connect all by itself just as if it were a *.dlo file. It is 
 MvdV>> obviously not just any ordinary file, it has the information as 
 MvdV>> the /where/ to send it, there is no need for an acompanying 
 MvdV>> *.?lo file that lists it.

 ml> the ?lo file is a zero byte file unless

 MvdV> I would rather put it the other way around. It is a file 
 MvdV> containing a list of files that should be send. Unless...

i stated the way i did because a flo file can be zero bytes to trigger a
poll... only if there is something to be sent that is not in XXXXYYYY.???
naming does that something need to be listed in the flo file... otherwise,
nothing needs to be listed in the flo file...

 ml> there's other traffic for the destination that must be listed in 
 ml> it... only files that do not conform to the XXXXYYYY.?ut (and 
 ml> maybe XXXXYYYY.REQ) format need be listed within them...

 MvdV> THe xxxxyyyy.req file must NOT be listed inside a *.?lo file.

correct...

 MvdV> It will be sent all by itself whenever a connection with the 
 MvdV> destination is established.

true...

 MvdV> One of the ways to initiate a connection is to have the sending 
 MvdV> system force a poll by creating a reduced flo file.

true...

 MvdV> To me this is illogical. Let the *.req initiate the connect on 
 MvdV> its own. 

then you loose the timing capability... you cannot create a req file with hold,
normal or crash status... there's no such thing as a ?eq file where the '?' may
be 'h', 'f', or 'c'... better to create it and let it sit until you are ready
to send it... that may be hours away or it might be after the next mail
tossing...

 ml> i have a script around here somewhere that goes something like this...

 ml>   bsofreq zone:net\node[.point][@ftndomain] somefile

 MvdV> Interesting and maybe some day I will make something similar. It
 MvdV> has very low priority though. Outgoing file requests are very
 MvdV> rare here these days. I might as well create the *.req file
 MvdV> manually.

i do that, too... then just drop it in the outbound with a similarly named flo
file... i have a couple of them already created which i just copy into the
outbound when i want to get a new copy of the referenced file ;) 

)\/(ark