On Tue, Oct 27, 2009 at 11:35 AM, Dale Worley <[email protected]> wrote:
> On Tue, 2009-10-27 at 11:15 -0400, Joly, Robert (CAR:9D30) wrote:
> > > I see that the code writes configuration information into
> > > ${TMP_DIR}/sipx.properties, but I don't see what directs
> > > Openfire to read that particular file -- is it hard-coded in
> > > the Openfire executable?
> >
> > Yes it is. sipXopenfire goes to look in /tmp for its properties file.
>
> If that is the case, the script should be structured to show that by
> creating a variable whose value is the file that Openfire will look in,
> and documenting it as such, rather than using the idiom used for "I need
> to put this file somewhere, so let's put it in a temporary directory."
>
I am guilty of this hackery. Now the variable will be called "somewhere"
and the place where it is used will be called $somehwere :-) This is in line
with the general principle of Computer Science - i.e. when in doubt use
indirection.
>
> Dale
>
>
> _______________________________________________
> sipx-dev mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
> sipXecs IP PBX -- http://www.sipfoundry.org/
>
--
M. Ranganathan
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
