Re: Re: Graph::Map and a Browser (no server side storing)

I've got a couple of thoughts here:

Create something now on a small load site so I have the "theory" down, and can expand onto a larger volume site
Disparity - The web app its pretty much all encompased within the CGI::Application framework, and having a seperate script kicking around loosens the bundle slightly.

Thanks for the point in "another" direction.. sometimes I just sit here trying to think around the problem and all I end up with HUA syndrome, and cant see the forest for the trees.

Comment on Re: Re: Graph::Map and a Browser (no server side storing)

Replies are listed 'Best First'.
Re: Re: Re: Graph::Map and a Browser (no server side storing) by rob_au (Abbot) on Apr 02, 2002 at 06:17 UTC
With regard to disparity, while I still think that your best method for handling temporary files will be through File::Temp, there is another option. If you are looking for something more permanent than anonymous STDIO streams and filehandle scope, for example if you wanted to optimise with some server-side caching (for which I would recommend Cache::Cache), you may want to explore the `teardown` method from CGI::Application. This method is called upon termination of the execution thread and allows for clean-up code to easily be incorporated into the CGI::Application framework. Most commonly, I make use of this method for the closure of file handles and database connections prior to script termination.	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: Re: Graph::Map and a Browser (no server side storing)
by rob_au (Abbot) on Apr 02, 2002 at 06:17 UTC

File::Temp

Cache::Cache

teardown

CGI::Application

This method is called upon termination of the execution thread and allows for clean-up code to easily be incorporated into the CGI::Application framework. Most commonly, I make use of this method for the closure of file handles and database connections prior to script termination.

[reply]
[d/l]