[Twisted-Python] Notes on switching twisted to new zope.interface code

[Eugene Coetzee]

Itamar Shtull-Trauring wrote:

>On Mon, 2004-07-19 at 16:31, Eugene Coetzee wrote:
>
>  
>
>>1) What is t.p.c  and 
>>    
>>
>
>twisted.python.components
>
>  
>
>>2) Why would one want to use Zope's interfaces in places of Twisted 
>>built-in interfaces
>>    
>>
>
>Next version of Twisted will use Zope's interfaces, so my comments were
>for developers so they can help port the code.
>
>  
>
Thanks for the clarification.

I am new to  Python, Twisted and Zope - so I guess I look at the world 
through my Perlish C++ tainted goggles :)

Just one or two comments - 30  000  feet from above.  I have noticed the 
introduction  of Zope interfaces in other projects as well where some 
developers are almost going bonkers with interfaces as "the new best 
thing" and where simple inheritance is being discarded in places where 
they should really be used. Don't think that is a good thing.      

IMHO - interfaces should be implented on the "boundries" of a component 
- i.e. those interfaces which form part of the API of a package. I get 
the impression that in Zope3 they are (ab)used to try and make an 
untyped language behave more like a typed language. This may work well 
in an app where performance is not a major issue - but in an networking 
framework  the abuse of interfaces may  lead to  an unnecessary and 
significant performance hit.

regards,

Eugene 
-- 
--
===============================================
Web                 -> www.reedflute.com
===============================================