[TYPO3-team-core-v5] Multi purpose URL scheme for the Flow world

[Adrian Föder]

Hi Bastian,
thanks for these 5 cents ;)

In the first run, I didn't think about a ViewHelper at all (I hope it 
didn't sound/read like this). It's really more about a Service or, 
especially, a conceptual thing.
Just at the very end this will likely result into a ViewHelper, which 
doesn't expect anything more than the "Flow URL". The ViewHelper gives 
it just through to the service, where various implementations from 
various packages wait for them to transpose the Flow URL to an HTTP URL 
for presenting it to the outside.

(But I'm just writing all that into a newly created #46526)

Cheers,

-adrian

Am 21.03.2013 21:05, schrieb Bastian Waidelich:
> Adrian Föder wrote:
>
> Hi Adrian,
>
>> well, just see my last comment here, http://forge.typo3.org/issues/45973
>> It's about, if you like, a correctly implemented "typolink"
>> functionality ;)
>
>
> Just my 5 cent before closing time:
> I find your approach interesting and we already thought about adding
> more custom stream wrappers (e.g. for the resource collections Robert is
> currently working on).
>
> Anyhow, I fear that we end up with s.th. like typolink (which is very
> flexible, but also very intransparent and hard to extend).
>
> Instead of putting all this logic into a ViewHelper (and thus in a
> string that "configures" the ViewHelper) I'd prefer a more generic
> approach.
> Frankly I don't know how that could look like precisely but maybe it
> would be just a "Link" TypoScript Content Element that can be wrapped
> around arbitrary other CEs..
>