TYPO3 Core

So what methods do you want to make public? And what do you want to hide?

Philipp Gampe wrote:

So what methods do you want to make public? And what do you want to hide?

That's what I was about to ask :)
Even if we simply encapsulate all the methods, that's still better than the current situation. I have to admit though, I haven't had a deeper look at HTTP_Request2. I just stumbled over this issue as I was looking for methods t3lib_http_Request offers and assuming it would be that way already (encapsulated).

Do you have a "must have" list maybe?

Do you have a "must have" list maybe?

Pretty much all methods.

It is already rather encapsulated. The real action is performed by adapters and of course by the observers if we attach any.

So what we could do is to add all method with phpdoc and a call to parent::method(). I am not sure if this make much sense, but I guess this is what you want to have.

We need all getters and setters and the send method. I fear there are not much more ;)

If we want to encapsulate, we would also need to encapsulate the response, which is HTTP_Request2_Response currently.

I am preparing some documentation on http://wiki.typo3.org/T3lib_http_Request
This is currently more a copy and past from the manual at PEAR
I will need to rewrite it to some smaller, more TYPO3 specific examples, but the current (very) big example should give you a start about what you can do and what you will need.

To me the class t3lib_http_Request is just a wrapper to set some TYPO3 config defaults. And that is the current state. The question is more what you to how and how you see t3lib_http_Reques: Is it just a config wrapper, a complete wrapper hiding the API or should it enable us to quickly change the underlaying framework.

If course I could give you a must have list from linkvalidator, but this wont bring as much further.
https://review.typo3.org/#change,4261