Development talk:File API: Difference between revisions
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
- dataroot/sessions | - dataroot/sessions | ||
- dataroot/upgradelogs | - dataroot/upgradelogs | ||
[[User:Martin Dougiamas|Martin Dougiamas]] 03:20, 28 April 2008 (CDT) : I don't see these as being in the API - I've updated the spec. | |||
2) Assuming we'll have a cool OOP FileAPI... | 2) Assuming we'll have a cool OOP FileAPI... | ||
| Line 17: | Line 19: | ||
- a) Will it support different FileAPI classes (to be able to store in other systems) ? | - a) Will it support different FileAPI classes (to be able to store in other systems) ? | ||
- b) Will it support multiple FileAPI classes working together (like the Repo) ? | - b) Will it support multiple FileAPI classes working together (like the Repo) ? | ||
[[User:Martin Dougiamas|Martin Dougiamas]] 03:20, 28 April 2008 (CDT) : Hmm, I suppose it makes sense to switch the backend from local file storage to specify something else (eg database storage) but multiple File storage places doesn't make sense to me, that is the Repository API and the Portfolio API. | |||
3) I've annotated in red some things that have sounded strange in my first look. | 3) I've annotated in red some things that have sounded strange in my first look. | ||
[[User:Martin Dougiamas|Martin Dougiamas]] 03:20, 28 April 2008 (CDT) : Thanks, all fixed. | |||
4) Are we going to have "directory records" in the implementation, or that is going to be handled exclusively by the "moodlepath" column? | 4) Are we going to have "directory records" in the implementation, or that is going to be handled exclusively by the "moodlepath" column? | ||
[[User:Martin Dougiamas|Martin Dougiamas]] 03:20, 28 April 2008 (CDT) : Good point. I was thinking of moodlepath only but I wonder if directory records might be more efficient. New table, I guess. | |||
5) One general question... are we going to "force" all modules to be "autocontained" ? How are we going to handle resources, for example (with all those css, links, images..). In general how are we going to handle multiple-file packages? | 5) One general question... are we going to "force" all modules to be "autocontained" ? How are we going to handle resources, for example (with all those css, links, images..). In general how are we going to handle multiple-file packages? | ||
[[User:Martin Dougiamas|Martin Dougiamas]] 03:20, 28 April 2008 (CDT) : they'll be a set of files, probably in a "directory" specified by moodlepath of directory record. What problems do you see? Should we retain better knowledge of the original group of files? | |||
That's all for now, ciao4niao :-) [[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 21:27, 5 April 2008 (CDT) | That's all for now, ciao4niao :-) [[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 21:27, 5 April 2008 (CDT) | ||
Revision as of 08:20, 28 April 2008
Some quick questions to avoid forgetting them:
1) Will them be under the control of FileAPI (or, as they are now, fixed local storage)?
- dataroot/temp - dataroot/lang - dataroot/cache - dataroot/environment - dataroot/filter - dataroot/rss - dataroot/search - dataroot/sessions - dataroot/upgradelogs
Martin Dougiamas 03:20, 28 April 2008 (CDT) : I don't see these as being in the API - I've updated the spec.
2) Assuming we'll have a cool OOP FileAPI...
- a) Will it support different FileAPI classes (to be able to store in other systems) ? - b) Will it support multiple FileAPI classes working together (like the Repo) ?
Martin Dougiamas 03:20, 28 April 2008 (CDT) : Hmm, I suppose it makes sense to switch the backend from local file storage to specify something else (eg database storage) but multiple File storage places doesn't make sense to me, that is the Repository API and the Portfolio API.
3) I've annotated in red some things that have sounded strange in my first look.
Martin Dougiamas 03:20, 28 April 2008 (CDT) : Thanks, all fixed.
4) Are we going to have "directory records" in the implementation, or that is going to be handled exclusively by the "moodlepath" column?
Martin Dougiamas 03:20, 28 April 2008 (CDT) : Good point. I was thinking of moodlepath only but I wonder if directory records might be more efficient. New table, I guess.
5) One general question... are we going to "force" all modules to be "autocontained" ? How are we going to handle resources, for example (with all those css, links, images..). In general how are we going to handle multiple-file packages?
Martin Dougiamas 03:20, 28 April 2008 (CDT) : they'll be a set of files, probably in a "directory" specified by moodlepath of directory record. What problems do you see? Should we retain better knowledge of the original group of files?
That's all for now, ciao4niao :-) Eloy Lafuente (stronk7) 21:27, 5 April 2008 (CDT)
