> From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > > From: Leo Sutic [mailto:[EMAIL PROTECTED]] > > > > > From: Leo Simons [mailto:[EMAIL PROTECTED]] > > > > > > ah. ok. So a component author declares "I need a T context" > > > and the container says "don't have one, so I'm not running > > you". Cool. > > > > Exactly. All it does is provide a method for component authors to > > declare their requirements (so that a container *may* > satisfy them if > > it can and wants to) in a uniform way. > > Which in effect discourages this type of use if the component > author values component reuse. Just from a practicality standpoint.
Yes, that is my conclusion as well. But it does make it possible to detect Phoenix blocks and run them if so desired, and it would explicitely acknowledge Phoenix's usage pattern as valid (as a special case of a general method). Berin, I have only heard from Leo Simons on the proposal. Do you have an opinion on it? (Just trying to see if a consensus can be reached, and if not, why.) /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
