On Mon, 23 Feb 2015, Michiel van der Vlist wrote to Developers:

 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.

the ?lo file is a zero byte file unless there's other traffic for the
destination that must be listed in it... only files that do not conform to the
XXXXYYYY.?ut (and maybe XXXXYYYY.REQ) format need be listed within them...

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

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

it figures out the proper outbound directory to place the ?lo and .req and then
creates the .req by simply echoing (in append mode) 'somefile' into the
properly named .req... it has already determined the proper name of the .req
and the .?lo file when it was figuring out the proper outbound directory...
handling the BSO format was a real bitch to do... that one portion of the
script is several hundreds lines long and it does 5D BSO... it would have to be
reworked a bit for 4D BSO... maybe one day i'll rewrite the script in pascal
and create a binary... perhaps one that can easily switch between 2D 3D 4D and
5D BSO formats ;) maybe...

)\/(ark