Ticket #3440 enhancement closed invalid
New t.w.client API & Backend
|Reported by:||tdavis||Owned by:||tdavis|
After a lot of testing and experimenting, I came to the conclusion that the current implementation of t.w.client (HTTPClient/HTTPClientFactory/getPage...) simply wasn't written to support persistent connections and couldn't come close to pipelining. I realized that even trying to make something that both worked with the current classes and worked with the new API would be way too difficult and kludgy to bother. So, I embarked on a mission into t.w2.client and found some code that is already up to the task.
Not a lot of changes were made to the t.w2.client code, except to remove the use of Streams and a couple other tiny things. The biggest thing t.w2.client was lacking was a usable API (at least that I could find) so it was never really a viable option. So, that makes up the bulk of the new backend whereas the API is completely new and only designed to work with the new backend. Current code will be marked as deprecated.
I will be posting code and tests for each piece of the new API as they are written. From there I will implement any recommended changes and reasonable features. The new backend will be posted last.