[TYPO3-dev] TYPO3 CMS 8 and REST API

Fabien Udriot fabien.udriot at typo3.org
Mon Apr 25 15:45:51 CEST 2016


Hi,

It is also my wish that TYPO3 CMS provides some defaults when it comes to REST API and more particularly in the Backend where we should better decouple things, enforce good practice and show the path on the FE side.

I have tested [extension Restler](https://typo3.org/extensions/repository/view/restler) and from what I have seen I quite like it. :)

* It is **fast** - more than with an extbase JSON view - thanks to a lightweight TYPO3 Bootstrap. You can add User Session handling "on demand".
* It is quick to setup and develop with.
* It has some nice API explorer via Swagger which is auto-generated by reading your code

I haven't thoroughly tested all the [feature set](https://github.com/Luracast/Restler/tree/3.0.0-RC6#features) but I definitely consider using it more intensively in my next projects.

One thing that bother me is it takes so long to reach 3.0.0. We are currently in [RC6](https://github.com/Luracast/Restler/tree/3.0.0-RC6) and the pace towards 3.0.0 looks slow - from what I see.

All the best,

Fabien

---
TYPO3 - inspiring people to share!
Get involved: typo3.org
On 24 Apr 2016, at 10:20, Michael Schams wrote:

> Hi Jürgen,
>
> Thanks for your feedback! Regarding TYPO3 core vs. extension: at the end
> of the day, I don't care if the core provides such a feature or an
> extension - as long as the extension is robust, stable/secure, actively
> maintained and follows the quality guidelines of the core :-)
>
> Keeping the core slim is also a good idea and general practise already.
>
> I can not assess if it makes sense more than for a feature like a REST
> API to have it in the core or as an extension (maybe someone from the
> core team has an opinion and wants to comment on this?).
>
> @Jürgen: do you have some concrete suggestions what should be changed in
> the core in v8 to make your life easier? Maybe it's worth a discussion?
> Maybe you can start an initiative?
>
>
> Cheers
> Michael
>
> On Fri, 2016-04-22 at 20:56 +0200, Juergen Kussmann wrote:
>> Hi Michael,
>> i have written the most code of the restler-extension....so i have a very big know how of it. In my oppinion, TYPO3 should not be the swizzer knife, which provide all possible features by the core. REST is an very good example. restler has a very big community in this topic and has very cool festures....why the TYPO3-core-team should try to reinvent the wheel? That make no sence and would cost a lot of time...BUT it would be very cool if we as extension-developer would have the possibility to 'integrate' third-party-frameworks more seemsless in TYPO3. The restler-extension is a good example for this: the extension use some core-methods (to bootstrap TYPO3 and override some bootstrapping) which extensions should normally NOT to use. But we use it to provide the best possible performance when calling an REST-endpoint...this could be done better/easier when there would be an API which could be used to e.g. bootstrap TYPO3 (e.g. bootstrap core, frontend, backend-user, database, caching-framework, load only defined extensions) inside an extension. Take a closer look inside the restler-extension and you will see what i mesn :-)
>>
>> Cheers,
>> Jürgen
>> _______________________________________________
>> TYPO3-dev mailing list
>> TYPO3-dev at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>
>
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev


More information about the TYPO3-dev mailing list