Timeline for Naming factory methods
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5 at 17:08 | history | edited | Basilevs | CC BY-SA 4.0 | added 65 characters in body |
| Jul 5 at 17:03 | history | edited | Basilevs | CC BY-SA 4.0 | added 65 characters in body |
| Jul 5 at 16:56 | history | edited | Basilevs | CC BY-SA 4.0 | added 252 characters in body |
| Jul 3 at 17:30 | comment | added | Greg Burghardt | Perhaps adding more information about the distinction between factories, suppliers, and providers would help readers to understand your answer. | |
| Jul 3 at 15:44 | comment | added | Greg Burghardt | Factories, providers, suppliers: they all imply that implementation details of object creation are abstracted away into a method. For example in C#/.NET, a provider usually combines application configuration with the factory pattern. The concrete type returned by a "provider" is typically an interface or abstract class. Furthermore, I don't think the distinction between factory, provider, or supplier matters much here. Object scope and lifetime are the major considerations. | |
| Jul 3 at 15:39 | history | answered | Basilevs | CC BY-SA 4.0 |