#1655: Create some kind of "component" architecture for TG2
------------------------+---------------------------------------------------
Reporter: mramm | Owner: plewis
Type: defect | Status: assigned
Priority: normal | Milestone: 2.1
Component: TurboGears | Version: trunk
Severity: normal | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by sevenseeker):
I currently am using zope.interface and find it quite nice. I also rolled
my own very similar interface that looked also like the Trac plugin
architecture.
Right now, I am doing everything through interfaces but will be switching
to using Abstract Base Classes as soon as I have time :)
This is because of my late and lazy binding which are not liked by pickle
and thus multiprocessing. ABC has features to allow this type of binding.
I have toyed with with using entry points as well.
All in all, I like zope.interface the best since it is out of the box and
I frankly was surprised I would like it at all. :)
Due to each having their place (strengths and weaknesses) perhaps instead
of discussing implementation at this point, we should discuss the reasons
for wanting a modular system and what the goals are. After all, the
golden question is as usual, "What exactly are you trying to do?"
--
Ticket URL: <http://trac.turbogears.org/ticket/1655#comment:16>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
