Support #3526

Support the new objpool HTTP connection-response model and simplify kamaki.clients.connection

Added by Stavros Sachtouris about 11 years ago. Updated almost 11 years ago.

Status:Closed Start date:04/02/2013
Priority:High Due date:04/10/2013
Assignee:Stavros Sachtouris % Done:


Category:kamaki Spent time: -
Target version:v0.8

Related issues

related to ./kamaki - Bug #3527: Some kamaki requests return "404 Not Found" Closed 04/02/2013


#1 Updated by Stavros Sachtouris about 11 years ago

This is fixed in 0.7.8 with a hotfix patch. In version 0.8. we should also expect a cleaner kamaki.client.connection package along with this.

#2 Updated by Stavros Sachtouris about 11 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

The kamaki.client.connection module is removed in this new implementation

The fat layer of connection classes has been replaced by two classes in kamaki.client module: RequestManager and ResponseManager
A RequestManager instance handles the info needed for a request, and can be used to perform the request, but explicitely
A ResponseManager instance performs the request only when needed (lazy). and caches the results for as long as it remains alive

IMPORTANT CHANGE: Each client request creates new RequestManager and RequestResponse instances

Unittests have been adjusted accordingly

#3 Updated by Stavros Sachtouris almost 11 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF