As Luis knows, my company has a LOT of handlers, and a LOT of Wirebox objects.
Wirebox retrieves the metadata on all our map() definitions in the binder once the config is loaded. Retrieving the metadata is a slow operation. No fault of Wirebox, just the way ACF does it.
What we’d like to see is a Coldbox setting (or Wirebox, whatever) that allows us to specify a larger timeout than perhaps is our default in Coldfusion. For example:
This would allow applications with a large Wirebox collection enough time to start up. This is important when performing the Coldbox startup. And if you’ve never compiled the code before (for us, a new variant after our releases), this is even more critical.
What is the possibility of the CB team adding such a feature?
I personally believe that when ColdBox is first initalizing and it can take up to 30-40secs secs or more sometimes on one production server and always get a timeout on the cfdirectory, etc.
So I believe that ColdBox should be setting this to some value that would ensure that the request does not timeout when ColdBox is setting up for first time use. Which is why I raised the ticket.
@Brad, this is very evident on ColdFusion 10 as it is on older version as well.
The problem with this is that it can be different on a per server basis. So I don’t see why should a user add this a their own customization in the Application.cfc as needed. Seems unnecessary to add this to the core.
I think the perception is that it is the framework only that requires that, so forcing every page (Which isn’t always a bad idea) isn’t something we see as our responsibility either. I mean I would look at it from the point of view, if it was going to cut down the amount of support questions as to why there is that initial timeout, I know which option I would be choosing.
