I've seen several tutorials explaining PHP installation under IIS as FastCGI recommending to set open_basedir to point to the folder or network path where the content of the Web site(s) is located.
When I set open_basedir on my application server, the following error showed up when managing files: Warning: open_basedir restriction in effect. File(C:\Windows\Temp\php92E7.tmp) is not within the allowed path(s): (C:\inetpub\wwwroot)
I understand I can set a temp directory under inetpub, but I don't see why is it a problem to use windows\temp.
Is there any safety flaw with PHP as FastCGI on IIS the demands open_basedir restrictions? If not, why is it recommended? Or is it not necessary? Is it possible to get open_basedir advantages using AppPool Identity with correct Permissions?