Project

General

Profile

Actions

Feature #20580

closed

streaming content

Added by David Bruchmann almost 15 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-06-05
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

short: I'd like to stream content.

description:
TYPO3 fetches content first (saving it in arrays first) renders it and
at the end the content is written.
In some special cases content is very large or/and needs much time
beeing fetched. In those cases memory-using and the whole way of
rendering are not able to serve the request (without AJAX) because
memory is exeeded.

request:
Id'like beeing able to hold only the footer in memory while header and
content are written directly.

consideration:
Ajax does allow requests after the page is send and will be better
because the page is rendered ready before getting the content.
Nevertheless JS is required (AFAIK) at the clientside and I thought
about a serversided solution.

(issue imported from #M11284)

Actions #1

Updated by Mathias Schreiber over 9 years ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback
  • Target version deleted (0)

is this still needed?

Actions #2

Updated by Alexander Opitz almost 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF