Hi,
I'm thinking about an app with with quite a few modules (10+) and I am
a little theoretically worried about the potential performance
issues related with it. My plan is to:
- use extremely few _init* methods in the application Bootstrap class
- use none _init* methods in the module's
Thanks Ralph,
This is very helpful. I will have to come back to this issue later on,
especially as I get a better handle on the framework, in general. You seem
to think that using the error handling functionality that comes with the
framework is the way to go. I am sure you will be vindicated on
On Fri, Dec 17, 2010 at 11:30 AM, Marian Meres marian.me...@gmail.com wrote:
Hi,
I'm thinking about an app with with quite a few modules (10+) and I am
a little theoretically worried about the potential performance
issues related with it. My plan is to:
- use extremely few _init* methods in
-- jalexander3 jeremy.michael.alexan...@gmail.com wrote
(on Thursday, 16 December 2010, 01:23 PM -0800):
This is very helpful. I will have to come back to this issue later on,
especially as I get a better handle on the framework, in general. You seem
to think that using the error handling
Caught exception: Unable to Connect to tcp://search.twitter.com:80. Error
#110: Connection timed out
Is there, maybe, a block to my site?
2010/12/12 Bartosz Maciaszek bartosz.macias...@gmail.com
2010/12/11 José de Menezes Soares Neto z...@detetive.net:
*Fatal error*: Uncaught exception
I think your DNS might be broken.
Try from the Terminal/CLI:
curl -I http://search.twitter.com/etc/pp
Twitter would respond with a status 400 if you get ratelimited.
Review the API docs for more:
http://developer.twitter.com/pages/rate-limiting#amilimited
Till
2010/12/17 José de Menezes
