Toolbox |
---|
![]() | This peer review discussion has been closed. |
I would like to move the article past Start-Class quality, a status that it's had for a while. Several improvements have been made by myself and others. Would like some guidance.
Thanks, Galhalee ( talk) 05:31, 9 August 2015 (UTC)
An injection is also about what is in control of the passing (never the client) and is independent of how the passing is accomplished, whether by passing a reference or a pointer.
Dependency injection involves four roles:
the service object(s) to be used the client object that is depending on the services it uses the interfaces that define how the client may use the services the injector, which is responsible for constructing the services and injecting them into the client Any object that may be used can be considered a service. Any object that uses other objects can be considered a client. The names have nothing to do with what the objects are for and everything to do with the role the objects play in any one injection. → None of this is attributed to a any citations or sources.
It's probably because this article is science/engineering related, but I don't really understand it. I find it quite confusing, but someone who has an interest in the subject probable makes complete sense to them! Hope my comments help you. Ping me if you have questions. — Calvin999 20:10, 28 August 2015 (UTC)
Toolbox |
---|
![]() | This peer review discussion has been closed. |
I would like to move the article past Start-Class quality, a status that it's had for a while. Several improvements have been made by myself and others. Would like some guidance.
Thanks, Galhalee ( talk) 05:31, 9 August 2015 (UTC)
An injection is also about what is in control of the passing (never the client) and is independent of how the passing is accomplished, whether by passing a reference or a pointer.
Dependency injection involves four roles:
the service object(s) to be used the client object that is depending on the services it uses the interfaces that define how the client may use the services the injector, which is responsible for constructing the services and injecting them into the client Any object that may be used can be considered a service. Any object that uses other objects can be considered a client. The names have nothing to do with what the objects are for and everything to do with the role the objects play in any one injection. → None of this is attributed to a any citations or sources.
It's probably because this article is science/engineering related, but I don't really understand it. I find it quite confusing, but someone who has an interest in the subject probable makes complete sense to them! Hope my comments help you. Ping me if you have questions. — Calvin999 20:10, 28 August 2015 (UTC)