[TYPO3-core] [Poll[ Integrate Speaking URLs in to TYPO3 CMS7

[Claus Due]

> ? Number of core extensions in 4.5: 56 ... master: 57

I've been counting a bit longer than that and as you may or may not
know, have on several occasions called for a long list of system
extensions that would be more sensible to ship separately.

But I digress. OT is also why I put that comment in parenthesis.

> The basic sf2 routing component relies on Request/Response. Current 
> master only got a rough request model, no real API for extension yet. 
> sf2 base routing can only do static routes, nothing dynamic at all. So 
> no route to your news record. That doesn't fit, not even on small scale.

If xyz consumes a configuration file the zyx can generate that file.
Dynamic doesn't imply that it must happen on each request. Even so:
the format used is fairly light and with the correct integration, even feeding
dynamic configurations might be possible.

Sure, the core doesn't have the parts we need. That's obvious. But the
other benefit of these measures would be a stricter and more dependable
model for request processing.

It might not be compatible with current realurl or even be able to use
TypoScript, but that's beside the point. Like I said: even very basic features
do have merit if you provide them with a nice toggle to switch it off and
let people use the TER-distributed realurl/coolurl/foobar extension.

But I shamelessly predict that if realurl becomes a system extension we will
very soon be seeing a double effort in maintaining that at the same time as
creating a new implementation (SF2 or not). And I wouldn't want that, when
the obvious alternative is to preserve realurl as TER extension - with added
contributions from the core team if that's required for compatibility.

> That doesn't fit, not even on small scale.

Then we make it fit. What we don't do is keep telling ourselves that it won't fit ;)