I'm from the school where exceptions are for moments where something happened
that a normal execution flow would not expect, like incorrect json format in
the response from API. Or user tried to access restricted content without being
authorized.
On the other hand, something like authorization
Anthony,
I'm not sure how the data will be submitted, but remember about user's
experience.
If you start processing just after user's input and processing will
take some time (based on the way the data will be submitted - HTML
form??), user (browser?) will probably have to wait for the response
f
If it's IIS7 than go for it.
If it's IIS6 than make sure to run it through FastCGI.
We are running IIS7 on Windows Server 2008 64bit boxes in production
and we are very happy with it.
Both, Zend and Microsoft, offer full stack installation packages.
Just remember that not all PHP features are
On Sun, Jan 3, 2010 at 7:03 PM, Hans Zaunere wrote:
> Saw this one, too - somehow my control panel doesn't look like this guy's.
> But, as far as I can tell, the FastCGI timeout is set to 600 seconds, which
> is far greater than the roughly 60 second timeout I'm seeing. Now I
> wouldn't bet the
I don't see anything wrong with PHP soap extension. It requires some
know-how, but is there anything faster and more reliable?
Suter
On Wed, Oct 28, 2009 at 5:54 PM, Rob Marscher
wrote:
> +1 for the soap extension as opposed to any library.
> ___
> Ne
