#15 Allow $DLC override with $FFWDLC

[Steve Southwell]

Bob Mirro writes:

Why don't we require the user to setup an environment
variable for each FFW WS Broker via Progress Exploder.
Something like:

Name: FFWDLC
Value: @{Startup\DLC}

That way this new environment variable won't effect any
existing DLC value that may have been set. Basically,
if you require the user to set this variable via the
Broker setup phase, you can reduce your above code to

OS-GETENV("FFWDLC")

and not have to worry about how to get the real DLC
variable. If that environement variable is not setup
properly, maybe you can output a message when the user
attempts to start the Broker.

Oh well, it's just an idea. It is one more step the
user would have to perform during setup, so I'm not
really sure if it's acceptable.

------------------------------------------
Steve Southwell responds:

That's a good idea, Bob. Actually what I think would
work well is to check for the FFWDLC first, and if it's
not there, then use the other methods. That way, it's
not required, but it's optional, if for instance one
wanted to use POSSE stuff instead of the regular DLC.

By making it an option instead of a requirement, we
keep with the goal of making an easy install.

Any opposition to putting this in FFW 1.1?

[Steve Southwell]

Logged In: YES
user_id=52644

There were no nays, so it's now part of FFW 1.1. $DLC can
be overridden by setting $FFWDLC as an environment variable.