Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Peaberry Activation: Support for factory cofigurations. #52

Open
mcculls opened this issue Jun 22, 2015 · 1 comment
Open

Peaberry Activation: Support for factory cofigurations. #52

mcculls opened this issue Jun 22, 2015 · 1 comment
Assignees
@mcculls
Labels
Peaberry-Extension Priority-Medium Type-Enhancement

Comments

@mcculls
Copy link
Member

mcculls commented Jun 22, 2015

Originally reported on Google Code with ID 49

We must have some consistent story about factory configurations. Seems it
is best to use the approach of iPojo where each instance of a factory
configuration defines a single instance of an iPojo component. Similarly I
plan to allow maximum one factory configuration per Injector. As
configuration instances are created and destroyed Injectros are created and
destroyed in sync. This might form the base of our component model.

Reported by Rinsvind on 2010-03-14 09:50:46
@mcculls
Copy link
Member Author

mcculls commented Jun 22, 2015

Reported by mcculls on 2012-08-04 21:42:19

  • Labels added: Peaberry-Extension

@mcculls mcculls self-assigned this Jun 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mcculls mcculls

Labels
Peaberry-Extension Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mcculls