| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
| Tip |
|---|
The future macro can be a handy way to avoid Confluence's default rendering timeout (normally 120 seconds) for request that are known to be long running any may sometimes exceed the limit. In these cases, it is best to also use with the Cache Macro to minimize the need for the extra processing. |
...
| Warning | ||
|---|---|---|
| ||
History
Originally an Atlassian ShipIt project, it was not maintained and eventually fell behind the times with Confluence 4. It has been spiffed up, fixed up, enhanced, and included with the Cache Plugin.
Here is a quote from Chrisopher Owen, the original author:
For Atlassian’s 7th ShipIt Day I implemented a Confluence macro that would defer rendering its body until the full page was received by the client. The body of the macro would then be sent back to Confluence for rendering via AJAX while the user was presented with a loading placeholder. As the rendering of the body occurs in the future with respect to the original page rendering pipeline, I called this functionality the Future Macro. It is ideally suited for rendering content that is retrieved from external sources where high latency can hold up the delivery of other content on the page.
Parameters
| Parameter | Default | Macro Browser | Description |
|---|---|---|---|
| title | blank | Title | Text displayed before rendering completes. Also will appear on the manual button. Helps user understand what information is going to appear. |
| manual | false | Manual | When specified, the section will only be rendered after the user presses the load button. The rendering proceeds in the background until available. |
| timeout | 120 seconds | Maximum number of seconds to render section | Timeout in seconds before the section rendering is abandoned. Once abandoned, a timeout error message will be displayed. |
...