> Consider using the duplicate method that Ray suggests- copy the application
> variables to the request scope and reference those guys in line. Then all
> you need is the initial locks for the write of the application variables and
> then a simple read lock around a duplicate function that moves those values
> into the request scope, which can be left unlocked.
What happens if you copy structures into the request scope? AFAIK a
structure copy like 'Request.s = Application.s' only copies a pointer to
the structure. Isn't there a problem when one template reads
Request.s.foo, while another template sets or modifies Application.s.foo?
Cheers
Michiel
--
Michiel Boland <[EMAIL PROTECTED]>
Digital Valley Internet Professionals
Plantsoen 17, Wageningen, The Netherlands
Phone: +31 317 465555, Fax: +31 317 460276
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
