Hi Michiel,

On 2015-02-23 11:42:48, you wrote to Developers:

 MvdV> Let's look at it from another angle. Forget about the docs or the
 MvdV> FTSC for the moment.

 MvdV> Question: Does it make sense that binkd waits for a connect to be
 MvdV> initited by the creation of a *.?lo file or would it be more logical
 MvdV> to have the *.req file initiate the connect all by itself?

 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 the
 MvdV> /where/ to send it, there is no need for an acompanying *.?lo file
 MvdV> that lists it.

 MvdV> So I propose that binkd initiates a connect when it finds a *.req file
in
 MvdV> the outbound, just as if it were . *.dlo file.

A good point...

 MvdV> To avoid backward compatibility problems, I suggest that it be made
 MvdV> configurable.

 MvdV> The keyword

 MvdV>   no-autosendreq

 MvdV> makes it behave as it does presently. When ommitted, the *.req file
 MvdV> initiates the connnect on its own.

To make it fully backwards compatible and not change the default behaviour,
with current config files, I would suggest the keyword:

  autosendreq

That will make it behave in the new way, when present.


Bye, Wilfred.

--- FMail-W32-1.69.1.95-B20140716