Difference between revisions of "Deferred.doc (MediaWiki)"
m (minor formatting; edit log) |
m (MediaWikiDoc:Deferred.doc moved to Deferred.doc (MediaWiki)) |
||
| Line 1: | Line 1: | ||
| − | [[Techniques]]: Software: [[MediaWiki]]: [[MediaWikiDoc:Developer Documents|Developer Documents]]: [[MediaWikiDoc:Deferred.doc|Deferred.doc]] | + | [[Techniques]]: |
| − | + | Software: [[MediaWiki]]: [[MediaWikiDoc:Developer Documents|Developer | |
| + | Documents]]: [[MediaWikiDoc:Deferred.doc|Deferred.doc]] | ||
==Contents== | ==Contents== | ||
| − | A few of the database updates required by various functions here | + | A few of the database updates required by various functions here can be |
| − | can be deferred until after the result page is displayed to the | + | deferred until after the result page is displayed to the user. For |
| − | user. | + | example, updating the view counts, updating the linked-to tables after |
| − | linked-to tables after a save, etc. | + | a save, etc. PHP does not yet have any way to tell the server to |
| − | way to tell the server to actually return and disconnect while | + | actually return and disconnect while still running these updates (as a |
| − | still running these updates (as a Java servelet could), but it | + | Java servelet could), but it might have such a feature in the future. |
| − | might have such a feature in the future. | + | We handle these by creating a deferred-update object (in a real O-O |
| − | + | language these would be classes that implement an interface) and | |
| − | We handle these by creating a deferred-update object (in a real | + | putting those objects on a global list, then executing the whole list |
| − | O-O language these would be classes that implement an interface) | + | after the page is displayed. We don't do anything smart like collating |
| − | + | updates to the same table or such because the list is almost always | |
| − | whole list after the page is displayed. We don't do anything | + | going to have just one item on it, if that, so it's not worth the |
| − | smart like collating updates to the same table or such because | + | trouble. |
| − | the list is almost always going to have just one item on it, if | ||
| − | that, so it's not worth the trouble. | ||
==Edit Log== | ==Edit Log== | ||
*'''2005-06-13''' Transcribed from docs for MediaWiki version 1.4.5 | *'''2005-06-13''' Transcribed from docs for MediaWiki version 1.4.5 | ||
Revision as of 14:30, 7 December 2005
Techniques: Software: MediaWiki: Developer Documents: Deferred.doc
Contents
A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user. For example, updating the view counts, updating the linked-to tables after a save, etc. PHP does not yet have any way to tell the server to actually return and disconnect while still running these updates (as a Java servelet could), but it might have such a feature in the future. We handle these by creating a deferred-update object (in a real O-O language these would be classes that implement an interface) and putting those objects on a global list, then executing the whole list after the page is displayed. We don't do anything smart like collating updates to the same table or such because the list is almost always going to have just one item on it, if that, so it's not worth the trouble.
Edit Log
- 2005-06-13 Transcribed from docs for MediaWiki version 1.4.5