I may be misreading your request, but you can edit the witango.ini
file so that the first place Witango looks is a central tcfs directory
that supports all of your applications. Just put your "ideal"
location first (and re-arrange the other suggested items as makes
sense to you).
We've been doing this for years... here's the line from our app
TCFSEARCHPATH=<@APPFILEPATH>;/tcfs/;<@CLASSFILEPATH>
In this case, we decided to have the apps look first in their own
directory, then in the "central" directory for all tcfs (/tcfs/).
(tcfs being located at webroot) However, we could just as easily have
set this to
TCFSEARCHPATH=/tcfs/;<@APPFILEPATH>;<@CLASSFILEPATH>
On Feb 22, 2008, at 3:10 PM, William M Conlon wrote:
N.B. I'm using the prefix COSR in the subject line to refer to some
future Community Open Source Release.
I'm noting this feature request on the list so;
* others can comment on the merits, security implications, vote for
it, offer a bounty, etc.
* it's documented somewhere, in case this feature request has not
made it into the v6 Commercial Release
TCFSearchPath is determined relative to the TAF that is executing,
which can easily result in Main Error Number: -815 (Cannot Locate
Object) if an application file is nested within a subdirectory.
Essentially, the utility of objects is frustrated because the server
configuration is intimately tied to the structure of witango-based
web sites. Consequently, I need to symlink the TCF source directory
into each directory containing an appfile that creates an object.
Better behavior would be to determine the TCFSearchPath relative to
<@WEBROOT>, so the TCFSEARCHPATH could be simply specified as, for
example, /TCFs/. Thereafter, all application files in a web site
would be able to locate the objects.
Still better behavior would be to support specification of an
absolute path using a leading slash, so that a master TCFs directory
could be shared among web sites. [The current behavior, where the
leading slash refers to the application file (why not use dot '.'?)
has caused some confusion among developers.]
This would be particularly valuable with Custom Meta Tags, which
could then be instantiated from any application file, anywhere.
Perhaps a simple compromise would specify both the tag definition
path (CUSTOMTAGSPATH) and the tag search path (CUSTOMTAGSSEARCHPATH).
Bill
William M. Conlon, P.E., Ph.D.
To the Point
2330 Bryant Street
Palo Alto, CA 94301
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
--------------
Dale Graham, PhD
Technical Manager, NIDB
NIH Intramural DataBase
Annual Reports, NIH Bibliography, Scientific Directory
[EMAIL PROTECTED]
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
