(on Saturday, 27 September 2008, 01:02 PM -0700):
>
> I recently created a new 6.01 eclipse project and discovered the usage of a
> plugin to initiate the application. I like this alot! Just out of curiosity
> though, I was considering extending it with a second abstract layer, so I
> can obtain these standard resources more fluently. Is this a valid
> implementation, or is there an unforeseen design flaw I might come across?
> Basically, I'd extend off this, initiating the registry oncreation, and
> well, you can see the rest.. pretty simple, but i am a bit hesitant and not
> sure why.
If you've paid attention to my webinars and presentations on SlideShare,
you'll notice I've been doing this myself for some time. Using a plugin
makes the bootstrap process incredibly simple and flexible -- and
easily re-usable for testing.
The one issue with it is that you have to ensure that the plugin handles
setting up your routes as well.
Several of us discussed (in separate conversations) the idea during
ZendCon, and we're beginning to revive the Zend_Application proposal,
but with a slightly different focus. Zend_Application would provide a
unified interface for setting up your application using a class
instance, and then allow dispatching the front controller. Keep an eye
on the proposals and provide commentary if you're interested.
--
Matthew Weier O'Phinney
Software Architect | matthew@zend.com
Zend Framework | http://framework.zend.com/
没有评论:
发表评论