Re: TclApp | DLL | CGI - permissions?
- From: "Jeff Godfrey" <jeff_godfrey@xxxxxxxxx>
- Date: Thu, 28 Jun 2007 19:51:13 GMT
"Uwe Klein" <uwe_klein_habertwedt@xxxxxxxxxxx> wrote in message
news:f7ddl4-nqs.ln1@xxxxxxxxxxxxxxxxxxxxxx
One reason this might be done ( unique path name ) could be
to manage concurrent multiple invocations of your wrappend app.
If you change over to a fixed path you will have to be carefull
with cleanup at exit.
Uwe,
Yeah, those are good points - and some that would definitely have to
be considered in a CGI environment. I've already modified my app to
just load a static DLL sitting in the same directory. This seems to
solve the immediate problem, and nicely avoids the ones you mention
above - which I hadn't yet thought about yet. I guess I'm best off
just sticking with that as a solution.
Thanks for the input.
Jeff
.
- References:
- TclApp | DLL | CGI - permissions?
- From: Jeff Godfrey
- Re: TclApp | DLL | CGI - permissions?
- From: Jeff Godfrey
- Re: TclApp | DLL | CGI - permissions?
- From: Jeff Godfrey
- Re: TclApp | DLL | CGI - permissions?
- From: Uwe Klein
- TclApp | DLL | CGI - permissions?
- Prev by Date: Re: TclApp | DLL | CGI - permissions?
- Next by Date: Re: Launching Tkcon with a main script and another as arguments
- Previous by thread: Re: TclApp | DLL | CGI - permissions?
- Next by thread: Re: TclApp | DLL | CGI - permissions?
- Index(es):