The possibilities of using Amazon EC2 and S3 to host or augment the performance and scalability of a Drupal install was discussed briefly last night at the Chicago Drupal Meetup (http://drupal.meetup.com/1/ ). I started to look into it today as I am evaluating moving to a new hosting situation.
I'm wondering why I have to disable and enable my module after every change to the code in the menu_hook before these changes are processed even though caching is disabled and I clear the cache tables every time the module is called. I'm sure this is a feature rather than a bug, but I'd like to know how to disable this behaviour during development because it's very time-consuming to disable/enable my module each time...