[TYPO3-v4] Webservices for TYPO3

[Fernando Arconada]

I dont feel ready (i'm not a senior TYPO3 programmer), but I think it is 
something that TYPO3 must have, it is something needed long time ago and 
seems that people dont want to face that problem

when TYPO3 people will face that problem?


El Thu, 19 Aug 2010 18:13:19 +0300, Dmitry Dulepov escribió:

> Hi!
> 
> Fernando Arconada wrote:
>> IHMO there are 2 way to get this ready: - a realurl modification
> 
> Feel free to make an add-on to RealURL but do not touch the code inside
> RealURL. It is too easy to break. This code is many years old and it is
> not the brightest and easiest piece of software. Many people supply
> patches but I usually have to fix those patches because they break
> something in RealURL. See below why it happens.
> 
>> - a realurl replacement, i.e. a flow3 web router backport
> 
> Try it... But make sure you test performance. RealURL was optimized for
> performance but still it is not fast. If you make link generation or
> resolving slower, it would not be good.
> 
> You also need to understand that RealURL, CoolURI, SimulateStatic and
> all such methods are not native to TYPO3. TYPO3 is not meant to work
> with speaking URLs by design. So all those extensions are big hacks. I
> doubt it is possible to make such router the right way with the current
> v4 architecture. I thought of that for a long time but it is simply not
> possible without major rewrite of FE part (tsfe, cObj, t3lib_page).
> 
> For example, when you decode, you need to know a lot and that
> information is not available, so you have to make guesses and fetch some
> data that technically you shouldn't. Also when encoding you have to
> assume many thing, which can be totally wrong (such as disabling ReaURL
> for the part of the tree or different speaking URL settings for
> different parts of the tree, or nested domains, or mount points, or
> skipping segments, or three different methods to mark the start of the
> site, etc). It is quite difficult to handle with the current
> architecture. If you feel ready, try it.
> 
> And remember performance...