| Poll: Expanded driver mechanism? You do not have permission to vote in this poll. |
|||
| yes | 9 | 64.29% | |
| no | 0 | 0% | |
| maybe | 5 | 35.71% | |
| Total | 14 vote(s) | 100% | |
| * You voted for this item. | [Show Results] |
| Expanded driver mechanism? |
For parsers.
Edit: email, translations (file or database based for example), maybe the Image library. I saw a scheme http://www.webiny.com/blog/2015/02/06/th...community/ with added abstraction - something that is called "bridge" between (external?) components. I don't know whether it is sane enough. I would use for now the term "driver" also for APIs that abstract the application from APIs of external components, installed with Composer or whatever other way. IMO it would be a good rule APIs of the external components with important common purpose (parsers, email) not to be used directly, but through interfaces provided by CodeIgniter. That would make external components replaceable. |
| Messages In This Thread |
|
Expanded driver mechanism? - by jlp - 04-11-2015, 08:36 AM
RE: Expanded driver mechanism? - by ivantcholakov - 04-11-2015, 12:32 PM
RE: Expanded driver mechanism? - by mwhitney - 04-13-2015, 11:39 AM
|
