t.p.components updates and cleanup

[twisted-trac]

	@itamarst reported
Trac ID	trac#98
Type	enhancement
Created	2003-07-16 23:07:39Z

Searchable metadata

``` trac-id__98 98 type__enhancement enhancement reporter__itamarst itamarst priority__low low milestone__ branch__ branch_author__ status__closed closed resolution__fixed fixed component__ keywords__ time__1058396859000000 1058396859000000 changetime__1091353806000000 1091353806000000 version__ owner__ cc__glyph cc__spiv cc__itamarst cc__etrepum cc__moshez ```

[twisted-trac]

	Automation removed owner

[twisted-trac]

	@itamarst commented

#!html
<pre>
http://peak.telecommunity.com/PyProtocols.html

</pre>

[twisted-trac]

	@radix commented

#!html
<pre>
I'm planning on starting up an interface-sig some time after
2.3 is released with the people who hack on PyProtocols and
the Zope interface system, with the goal of unifying them
all into one standard system and adding it to the python stdlib.

Just because there's no better place for me to record these
thoughts, here's how I figure it'll progress:

* Identify each feature / property in all of the systems
* Identify the ways which they conflict
* Find reasonable solutions to the conflicts, via
  parameterization or other ways
* Hack
* PEP
* Contribute
* Death to interface-sig

</pre>

[twisted-trac]

	@moshez commented

#!html
<pre>
Please also look at sandbox/moshez/components.py for an improvement suggestion

</pre>

[twisted-trac]

	@itamarst commented

#!html
<pre>
Another data source -
http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ComponentArchitectureSimplification

Scroll down to the bit about "Adapter Enhancements", the rest isn't all that
relevant to us (it has a proposal for adapting from multiple objects -- woo
multiple dispatch -- and an algorithm. And class adaption, which we already do.)
</pre>

[twisted-trac]

	@glyph commented

#!html
<pre>
This looks like an efficiency disaster!  If a user passes a 5- or 
6-element tuple to the component system, I could imagine the server 
blocking for *minutes* trying to figure out how to deal with that before 
failing.
</pre>

[twisted-trac]

	@itamarst commented

#!html
<pre>
Bob had a use case for being able to adapt classes to classes, rather than just
classes to interfaces. Something to do with class methods.
</pre>

[twisted-trac]

	@puzzlement commented

#!html
<pre>
Assigning this bug to itamar, although I guess the port to zope components isn't
exactly what was meant. You can resolve it if no longer relevant.
</pre>

[twisted-trac]

	@itamarst commented

#!html
<pre>
Port to z.i should deal with this.
</pre>